Trending Topics: Latest from our forums (August 2021)
See how our most popular recent threads on StackOverflow 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 August 2021. You too can ask questions by using the tag docusignapi in Stack Overflow.
Thread: You have not granted or have revoked your consent to be impersonated by Docusign Apps Launcher
https://stackoverflow.com/questions/68597387/
Summary: The developer is using Docusign App Launcher in Salesforce and is getting a consent error related to authentication to Docusign.
Answer: Docusign eSignature for Salesforce, as well as the Apex Toolkit for developers building Salesforce integrations using Docusign APIs, require that you authenticate to Docusign to make API calls. The chosen method of authentication is using JSON Web Token (JWT) Grant and that means that the app is using the credentials of a single user to make API calls. That requires the app to impersonate that user and requires that consent be given at least once by the user. Consent can be obtained individually or for the entire organization. Also note that the UI for the Salesforce App Launcher is opening a new dialog for consent, and if the browser’s pop-up blocker suppresses this, you will not be able to give consent and will eventually get the above error.
Thread: C#.Net Docusign Signature Position
https://stackoverflow.com/questions/68789525/
Summary: This developer is building an integration for Docusign Signature Appliance (DSA) using C# and is having issues positioning signature elements.
Answer: The Reason Tag that the developer was trying to use is reserved for specific usage in the PDF being signed. The Title Tag is a general purpose tag that is more suitable for the developer’s needs (in this case, “Additional Information”).
Thread: Docusign : login without user consent
https://stackoverflow.com/questions/68626413/
Summary: The developer is interested in building an integration using Java. They would prefer that the end user doesn’t need to log in to Docusign or provide consent.
Answer: JSON Web Tokens (JWT) authentication enables developers to request a token on behalf of some user without that user having to log in. That means that except for the first time, when the user has to consent, there's no web UI required to obtain a token. This is the best option to avoid end users having to log in to Docusign, but consent is needed once. The developer can find code examples in Java showing how to use JWT in GitHub.
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
