I get the url back from the RecipientView which I then update the window.location.href with.
When I am directed to the DocUSign contract window, I am unable to sign the contract or see my text tab.
I get the below error. What is the best way to resolve this?
demo.docusign.net/:1 Access to script at 'https://a.docusign.com/ds_arya_wrapper.min.js?f=1' from origin 'https://demo.docusign.net' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
demo.docusign.net/:384
GET https://a.docusign.com/ds_arya_wrapper.min.js?f=1 net::ERR_FAILED
Below you can only see one app listed in the CORS allowed list and the particular app I am working with is not there?
If I go to edit the setting of my particular app, I can add a URL to the CORS but it has to be https whereas I am currently on http:localhost as I am building the app.
In your comment you say:
the Next.js server calls the DocuSign ApI. Then the front-end of Next.js calls my backend Next.js API
In this case, your Next.js app is not using CORS. The front-end is calling the back-end, then the back-end (the server) is calling DocuSign. This is a standard web app configuration. It works great and it is not using CORS.
Use the Apps and Keys page to add the origin http://localhost
to your client ID (integration key) configuration. Using http://localhost is only supported on the developer platform demo.docusign.net.
All other other CORS origins must use https.
On the DocuSign production system, you must use https. (You can use https://localhost, but not with a self-signed server cert.)
Then, on the CORS section of the settings tool Check that you're allowing CORS by default
Then run your application After it makes a successful CORS call, you'll see http://localhost
as an origin for your application listed on the CORS page