Integrate Countersignature Consent with airSlate SignNow

Integrate esigning consent

From DocuSign, consent required, individual consent. I'm Larry Kluger, a lead product manager on the DocuSign developer team. DocuSign supports three different OAuth flows for our APIs, authorization code grant, JWT grant, and implicit grant. See the show notes for links to a video and documentation about the OAuth authentication flows. To meet modern information security standards, an authorized person must provide consent before an application can act on behalf of, or impersonate a user. Application consent is tracked by DocuSign. It is not stored in a cookie or elsewhere on the browser. The authorization code and implicit grant flows smoothly handle the consent step when the user authenticates with the application for the first time. This is called in-band consent. Since it occurs within the application flow. In-band consent is not available for the JWT grant since a JWT grant is used by autonomous applications where users often not present. For JWT grant and out-of-band, consent step is needed. Because in-band consent is more convenient, DocuSign recommends that independent software vendors, ISVs use authorization code grant whenever possible. DocuSign supports three options for JWT out-of-band consent, administrative consent, individual consent, and ISV administrative consent. This video discusses individual consent for the JWT grant. ISV administrative consent is required if an ISV application, whose integration key is managed by the ISV is, configured to use administrative consent for users on your account. Many ISVs use individual consent, which can always be used since it can be used by any DocuSign customer with any type of account. If you receive the consent required error, well, the first thing is congratulations. Receiving this error when you're using the OAuth JWT grant flow indicates that your application is creating the JWT request correctly. That covers a lot of software territory. Next, you just need to obtain consent for the user, your application is impersonating, and you'll be ready to make API calls. Individual consent is the lowest common denominator JWT consent flow. It can be used for any JWT scenario. To use individual consent, the account user who will be impersonated via the JWT authentication flow must log in to the DocuSign web app. For system accounts, such as finance@example.dom, you must have access to the user accounts email and the DocuSign password for the account. You should also prepare a suitable Thank You page that will be shown to your application's users after they have granted consent. I'll discuss the example Thank You page later on in this video. Now let's look inside the individual consent process. It's important to realize that the individual consent process is actually the first part of the authorization code grant flow. But we'll end the flow early. Here's how it works. Step one, the user granting consent opens a URL from their browser. The URL is also called the consent URL. The URL is a request to the DocuSign URL service provider, either account.docusign.com or account-d.docusign.com. Consent URL includes the application's client ID, the integration key,...