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

JWT Authentication Failing After Integration Key Promotion - issuer_not_found Error

  • January 28, 2026
  • 1 reply
  • 31 views
D
Newcomer

Description:

I'm unable to authenticate using JWT Grant with my promoted integration key in production. I receive an issuer_not_found error despite having the integration key properly configured.

Configuration:

  • Integration key was created in developer account and promoted to production using DocuSign's go-live process
  • Generated new RSA key pair in production
  • User Application setting: Yes
  • Authentication Method: Authorization Code Grant
  • Redirect URI: http://localhost:8080/callback

Error:
When attempting JWT authentication, I receive:

{"error":"invalid_grant","error_description":"issuer_not_found"}

Steps Attempted:

  1. Tried granting individual consent via multiple authorization URLs (both account.docusign.com and account-d.docusign.com)
  2. All consent URLs fail with "The client id provided is not registered with Docusign"
  3. Verified all User ID, Account ID, and Integration Key values match between production account and application configuration

  4. Confirmed RSA key pair is properly configured

  5. Attempted granting consent via authorization URL provided by Docusign support (Token endpoint: account-eu.docusign.com/oauth/token). Account-eu.docusign.com does not resolve in DNS either in USA or EU (attempted on 4 different devices, in 4 different global locations)

UPDATE: I've tested authorization from both US location (original) and EU location (IP 9.160.161.135). Both locations return the same error: 'The client id provided is not registered with Docusign.' This confirms the issue is NOT geo-routing.

1 reply

T
Docusign Employee
Forum|alt.badge.img+5

Hi.

It looks like you are using incorrect URL’s for the account server, there is only
demo: https://account-d.docusign.com
production: https://account.docusign.com

If you cannot generate the consent URL, then either the client id you are using is incorrect, or the account server url is incorrect.

It is documented here with examples:

https://developers.docusign.com/platform/auth/consent/obtaining-individual-consent/

First determine if this is working:

An integration key identifies your integration and links to its configuration values.

1. Open the Apps and Keys Page.

2. Under My Apps / Integration Keys, select your App / Integration Key.

Use the following consent URLs, just replace REPLACE_WITH_INTEGRATIONKEY with your integration key

Demo

https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=REPLACE_WITH_INTEGRATIONKEY&redirect_uri=http://localhost:8080/callback

Production

https://account.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=REPLACE_WITH_INTEGRATIONKEY&redirect_uri=http://localhost:8080/callback

If you get the following errors:

The client id provided is not registered with Docusign.
This means your integration key specified is wrong.

 

Code of ConductAccessibility statement

Docusign Community

Code of Conduct