Trending Topics: Latest from our forums (September 2023)
See how our most popular recent threads on Stack Overflow can help you solve your own development issues.
Table of contents
Here are some of the latest popular questions that the Docusign developers community asked on Stack Overflow in the month of September 2023. You too can ask questions by using the tag docusignapi in Stack Overflow.
Thread: Docusign: No 'Access-Control-Allow-Origin' header
https://stackoverflow.com/questions/77038191/
Summary: The developer is building an integration that uses embedded signing. They created an envelope and redirected the browser to the embedded signing URL, but cannot sign the envelope. They see what they believe is a CORS-related error in the browser developer tools window.
Answer: The developer is confused. They’re not using CORS, the error message they see is an internal Docusign error (which is not causing the problem they think they have). The reason for their issue is that they didn’t add any tabs to the envelope. CORS was a red herring in this situation.
Thread: Docusign JWT Auth Error while requesting server, received a non successful HTTP code with response Body
https://stackoverflow.com/questions/77055896/
Summary: The developer is using the Docusign eSignature C# SDK and is trying to obtain a JWT access token. They are getting a 500 error message from the Docusign server.
Answer: The issue in this case turned out to be using the wrong version of the TLS protocol. Docusign requires that all HTTP calls use version 1.2 or above. The calling server may have been using version 1.1, which Docusign no longer supports.
The Docusign C# SDK does not set the version of TLS; when using C# code, the version is set by the server and the rest of the C# application.
The following two lines of code may be needed in situations where your code runs in the context of a legacy application or on an older server that still uses TLS version 1.1:
ServicePointManager.Expect100Continue = true;
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
Thread: How to Integrate Docusign with your CodeIgniter web application using Postman?
https://stackoverflow.com/questions/77064259/
Summary: The developer is using CodeIgniter with PHP and is having problems adding the Docusign eSignature PHP SDK to their code using Composer.
Answer: Since CodeIgniter uses PHP, the best way to ensure you have everything you need to start coding with Docusign is to use our Quickstart. This way you get all the code needed in a ZIP file that is also customized with the configuration information needed for you to authenticate and get access tokens to make API calls.
Additional resources
Inbar Gazit has been with Docusign since 2013 in various engineering roles. Since 2019 he has focused on developer content. Inbar works on code examples including the launchers, available on GitHub in eight languages, and helps build sample apps showcasing the various Docusign APIs. He is also active on StackOverflow, answering your questions. Inbar can be reached at inbar.gazit@docusign.com.
Related posts
Discover what's new with Docusign IAM or start with eSignature for free
