Back to Docusign.com
Hi everyone,
After completing the Go-Live process for our integration, I'm unable to complete JWT consent because our production account has zero registered Redirect URIs, and any attempt to add one fails.
Setup:
- Integration Key created and verified on a Developer account, then promoted to Production via Go-Live
- RSA keypair generated successfully on the production app (visible under Apps and Keys → App Details)
- Authentication Method currently shows as "Authorization Code Grant" with zero Redirect URIs registered
The problem:
Going to Apps and Keys → [App] → Edit → Add URI → entering a valid HTTPS URL → Save consistently returns:
"This integration key could not be updated. Please try again in a moment."
Tried: multiple browsers, incognito mode, multiple URLs, retrying over several days. Same error every time.
What I found in the docs:
DocuSign's own "After Go-Live" guide states Redirect URIs should be configurable on the production account ("OAuth Management Account") directly. It also mentions an alternative: Organization administrators can proactively grant scope permissions to the integration key. However, our production account doesn't have an Organization layer, so that workaround isn't available either.
What I've tried:
- Adding the Redirect URI on a separate Developer account (same Integration Key) — this succeeded, but doesn't propagate to the Production account
- Contacting DocuSign Support — got pointed to standard documentation steps (which I'd already tried) and ultimately told this is outside Standard Support Entitlement scope
Has anyone run into this specific "could not be updated" error on a production app, or knows of any other path to register a Redirect URI / get JWT consent working in this situation? Any pointers appreciated.