09-04-21 02:04 PM
12-04-21 01:20 PM
12-04-21 03:05 PM
"Here's a few things to check:
aud
value - must be exactly account-d.docusign.com
(for demo) or account.docusign.com
for prod. Including https:// or any other value will fail.
sub
value - must be an active userID (in GUID format) in the appropriate environment.
iss
value - must be a valid client ID
Private Key used for signing - must be associated with the Client ID in the correct environment. If you're using a key generated in Production but the assertion is directed toaccount-d.docusign.com
it will fail. In some cases it can take a few minutes for a newly generated keypair to be valid in the Account Server, so if you've just generated that key, wait a bit and try again."
Original Source: docusignapi - Curl Command throwing' invalid grant error' on Windows command line - Stack Overflow
12-04-21 03:31 PM
Hi Eric,
We are facing issue in Configuration Step 2 of Get User Consent, when I paste the url created by us infact we are getting the prompt to log into the DocuSign account but after entering the credentials we are not getting the window to confirm that this application may sign and impersonate on behalf of the account and it seems we are failing at creating the redirect URI
Are there any specifications to be followed for Redirect URI?
Regards,
Bhaskar