Skip to main content
arrow-left Back to Docusign.com
Solved

Go Live Review failed

  • January 24, 2025
  • 2 replies
  • 129 views
J
New Voice
Forum|alt.badge.img+2

Hello! 
I have got a Go Live status: Review failed (See OAuth 2.0 migration options).
After reading the doc I do not understand what we are doing wrong.
Here are the 2 types of calls I do:
/oauth/token
/clickapi/v1/accounts/{accountId}/clickwraps/{clickWrapId}/agreements
We have chosen JWT grant authentication.

Can you help me understand what is wrong?

Thanks a lot!

Best answer by Islam.Hassanein

Hi ​@justinem,

Could you please double-check the following:

  1. Ensure that the user has granted consent.
  2. Verify that your JWT payload contains the correct claims (iss, sub, aud, scope) and that each claim has the appropriate values.
  3. Ensure that your /oauth/token call successfully exchanges the JWT for an access token.
  4. Make sure both signature and impersonation scopes are included.

To meet Go Live requirements, you can create 20 new envelopes. For more information, refer to the Go Live Requirements Documentation https://developers.docusign.com/docs/esign-rest-api/go-live/

If the issue persists, please open a support case and provide the specific integration key to assist you in resolving the issue quickly.

2 replies

I
Docusign Employee
Forum|alt.badge.img+6
  • Islam.HassaneinDocusign Employee
  • Docusign Employee
  • Answer
  • January 26, 2025

Hi ​@justinem,

Could you please double-check the following:

  1. Ensure that the user has granted consent.
  2. Verify that your JWT payload contains the correct claims (iss, sub, aud, scope) and that each claim has the appropriate values.
  3. Ensure that your /oauth/token call successfully exchanges the JWT for an access token.
  4. Make sure both signature and impersonation scopes are included.

To meet Go Live requirements, you can create 20 new envelopes. For more information, refer to the Go Live Requirements Documentation https://developers.docusign.com/docs/esign-rest-api/go-live/

If the issue persists, please open a support case and provide the specific integration key to assist you in resolving the issue quickly.

J
New Voice
Forum|alt.badge.img+2
  • justinemNew Voice
  • Author
  • New Voice
  • January 27, 2025

Hello ​@Islam.Hassanein!

Thanks a lot for your answer.
I verified all your listed points, and it seems it is all good, but I still have a ‘Review failed’ with the same reason. 
For information, I am using the ‘docusign-esign’ node SDK, and I am using the requestJWTApplicationToken function to generate the access token. Do you confirm it is compliant with OAuth 2.0?

To open a support case, it seems I need a production account, and I do not have one yet. 
Can the issue be linked to the fact I do not have a production account (I mean having a production account being a pre-requisites to Go Live, and so my review failed because of this)? 

Thanks again!

Code of ConductAccessibility statement

Docusign Community

Code of Conduct