Hi.
I’m now trying to use DocuSign Extended Plugin but facing the issues like this.
I’ve checked the keys and JWT tokens but that was all okay.
So I have looked the plugin integration demo and finally understood that they are using different integration_keys in plugin config and JWT creation stage.
Is there anybody who have faced this kind of issues before?
Thank you.
Hi @Bruno! Thanks for reaching out.
First of all, could you please make sure all the steps are configured properly according to our docs for the “send without auth” call?
If all the steps look correct on your end, can you please help us by providing a bit more details like steps to reproduce the issue, plugin setup screenshots (workflows, plugin tab), or maybe would be better a screencast (You can use Loom to record the screen). Anything that could help us to understand what can cause it. 
Thank you! Looking forward to your reply.
Best regards,
Gulce
Thank you for reply, @Gulce
I’ve followed all steps according to the docs for the “send without auth” call.
And I also promise that all things are correct in my side.
Something I can’t understand is, “integration key” difference during the plugin config stage and JWT creation stage in the documentation.
Below is the image in documentation(DocuSign Extended).
“integration key” in plugin config stage starts with “1fcbc…”
and “integration key” in JWT creation stage starts with “3e5d…”
How can it be different yet its for the same app?
Hi @Bruno,
Thank you for your patience.
The different integration keys are shown as examples only. As you can see from the screenshots, the projects are different.
So in your case, you just need to use your project’s integration key and user id as shown in the example. Please let me suggest you check your keys if they are set up properly. They might be not correct therefore you get an 400 error.
Or, please share a video recording showing your entire setup to let me understand what might cause this issue. Like your console (keys, etc.) , plugins tab, and workflow.
Thank you!
Best,
Gulce
Hi, Gulce
Thank you for your support.
I can’t understand why the zeroqode demo “docusign extended plugin” uses the different integration keys in plugin config and JWT creation.
This is the demo app url
Here the integration key in plugin config is set to a6cefb5c…
In contrast to this “DocuSign send without auth” step in workflow contains this JWT.
eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiIzZTVkZDI0Mi0wMDE4LTRkMDItYmJkMy01NzgzYjFlYmI1N2QiLCJzdWIiOiIxZjJjZmY1NC1mMzQ1LTRhNDYtOWJlMS1iYjk2MzAxM2U1ODQiLCJhdWQiOiJhY2NvdW50LWQuZG9jdXNpZ24uY29tIiwiaWF0IjoxNTU4NzM2OTkyLCJleHAiOjE4NTg3NDU5OTIsInNjb3BlIjoic2lnbmF0dXJlIGltcGVyc29uYXRpb24ifQ.EY8PSCyW1EitZSUKWesTdZKCXPUUwgFhOyK6FVFsDArSOg9KxGMbhZsWZlHj3wxY63mwe7S9U1JtcONO7sHLJ5u1J4RQ5WOdd7sPTe8CXYKqtTnPaHmKVR2T4FVhoS9nF2lY20ZXurhTEUYD18ueAmILhwRcoBKzMImHESl6LbgyQZh7x_T7hepA3ckuUpWftaWuyhj3GpD2DLAvtQBPXRugOz8v_c5ty9T2D5Pfvr7GjtfE8y8d1j9tNqVb3zVxNDJ9b5LFt6F1Gf6yu3QuF9ijLFWVIMSKu4jsIJ78XyaPtSE2Q1lG5w76LvXPYzjdX3r1hnBzbhd_3LVlfIakNA
And what I have decoded this JWT, I can get this integration key(3e5dd242…).
As you can see both integration key is different although it should be the same in all app flow.
How can I understand this?
Thank you.
Bruno
Hi @Bruno,
Thank you for your message.
Yes, we are using a different project in DocuSign Send Without Auth action and JWT token creation. However, please note that this does not affect the behavior of the plugin. We just use these keys as an example and it doesn’t have to be the same app. Therefore, you can use any app integration key you want to create a token. It could be a different app or the same app keys that you’re using in the plugin tab.
So, if you have an application and you want to set this flow only for that application, simply complete the steps we show in our documentation to generate a JWT with the same application keys you used in the plugin tab.
Please let me know if you need further clarification at this point or have any other questions.
Best regards,
Gulce
Hi, @Gulce
Thank you for your detailed explanation.
But in zeroqode-demo-12 app, if we change the integration key in JWT to same as in the plugin config, then it will face 400 error(you can see the error image in the first section).
Please try my way.
And something also can’t understand is, in demo app it uses “DocuSign Extended Testing” plugin, though I can’t use that plugin in the development process.
Regards
Bruno
Hi @Bruno,
Let me please test it on our end, I will get back to you as soon as possible.
On our demo apps, all our plugins have the “Testing” word in their names because these plugins are connected directly to the app. It is done this way to let us check the changes made to the plugin code immediately, before pushing the commercial plugin update.
Best regards,
Gulce
