Skip to main content
Question

403 Error When Another Docusign User Attempts to Login

  • 19 August 2024
  • 7 replies
  • 61 views

In the network tab, the error message reads: {"errorCode":"Missing_Config_Or_Request","message":"The request is missing or the account does not have the right permissions. Please check and try again."}


Right now, I have embedded Docusign Esigning into an application (still demo endpoints if that is noteworthy), and I am at the point that once you click “Esign”, user is redirected to Docusign login page 

https://account-d.docusign.com/oauth/auth...

From the login page, we go through the OAuth Code Grant method. Then, once user logins in an envelope draft is created and etc…

 

However, the current error is occurring on the creation of the envelope 

https://demo.docusign.net/restapi/v2.1/accounts/${r.accountId}/envelopes

 

I noticed, when I login with the account that I created the integration key with I don’t receive this error, but when I login with a different Docusign account, I receive this error

Can you provide the error you are experiencing on the creation of an envelope, this will help analyze the issue.

@Troy.Winterbottom  
I did; it is a 403 error and in the network tab it reads: {"errorCode":"Missing_Config_Or_Request","message":"The request is missing or the account does not have the right permissions. Please check and try again."}

is this a CORS request to the other account? https://www.docusign.com/blog/developers/cors-here

The error is listed here: https://www.docusign.com/blog/developers/better-cors-error-messages-developers

To maintain security, the client ID (integration key) must be configured with the website origins that will make CORS calls to Docusign. Add the CORS configuration information to your client ID via the eSignature settings application, in the Apps and Keys page.

In addition, your access token must include both the signature and cors OAuth scopes. Finally, each eSignature account that will use your CORS application must allow CORS access. By default, CORS access is allowed.

The last paragraph could be related to your issue, please ensure CORS access is allowed in this other Docusign account that is using your integration.

Finally, each eSignature account that will use your CORS application must allow CORS access. By default, CORS access is allowed.

@Troy.Winterbottom 

 

What do you mean by if its a CORS request to the other account?

 

I have a Docusign integration embedded into my application, and another Docusign user/account is logging and attempting to use the integration (not the user/account that created the integration key), which leads to the 403 error on envelope creation. 

When the user grants consent to your application with their Docusign Account, they are limited to the configuration/constraint on their account.

Is your integration using CORS?

If yes, you will need to ensure users of your application/integration have CORS enabled on their Docusign account.

@Troy.Winterbottom 

How do I ensure they have CORS enabled, and what if it is enabled? 

You can provide the following documentation to other users that are using your integration to enable CORS on their account:

https://developers.docusign.com/platform/single-page-applications-cors/enable-disable-cors/

On that page, it is under the heading: Update account default CORS setting

Reply


Code of Conduct