Trending Topics: Latest From Our Forums (March 2020)
Latest popular questions that the Docusign developers community asked on Stack Overflow in the month of March 2020
Table of contents
Here are some of the latest popular questions that the Docusign developers community asked on Stack Overflow in the month of March 2020. You too can ask questions by using the tag docusignapi in Stack Overflow.
Thread: Is Docusign using up-to-date TLS cipher suites?
https://stackoverflow.com/questions/60523903/
Summary: The developer is setting up eventNotification in the envelope so that they can get Docusign Connect events from Docusign servers to their servers. This communication is using TLS protocol for encryption. The developer is interested in using a modern set of cyphers that includes some new TLS 1.3 cyphers that are not yet supported by Docusign.
Answer: Docusign continuously evaluates new industry security standards and ensures that all our services are using the most secure communication. At present time, some newer TLS cyphers that use TLS 1.3 protocol are not yet implemented. We hope to have these updates in the future.
Thread: Docusign From Demo to Live
https://stackoverflow.com/questions/60715002
Summary: The developer is using legacy authentication and is having an issue after they promoted their integration from demo to production. They’re getting an error message that says “One or both of Username and Password are invalid” despite entering valid credentials.
Answer: when building applications using Docusign APIs, developers have to start first by using the developer sandbox (“demo”), and once ready, promote to production. The production environment includes many different datacenters with different URLs, unlike demo, which only includes a single datacenter with its URL. Therefore, if you make an authentication call to the wrong URL in production and you’re using legacy authentication, you’ll get an error message saying your password is invalid even when it's the correct password. Docusign highly recommends that you do not use legacy authentication, as it’s not as secure and is outdated. If you do still choose to use legacy authentication, you will have to determine which set of servers or which URL to call when making the authentication API call.
Thread: Docusign embedded signing - how to get the URL of the document that contains signature?
https://stackoverflow.com/questions/60706172/
Summary: The developer is asking how they can programmatically obtain a URL that can be used to facilitate envelope signing. Answer: This is what we call embedded signing, and is one of the most common ways developers use the eSignature API. There are lots of ways to learn how to use this functionality. For example, we have a code example, available in different languages, that showcases and explains how to use embedded signing so that you can obtain a URL for this purpose.
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
