Carbon Copy Digisign Consent with airSlate SignNow

Integrate digisign consent

From DocuSign, Consent_required,  Administrative consent. I'm Larry Kluger,   lead developer advocate for DocuSign. DocuSign  supports three different OAuth flows for 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 authentication flow.  In-band consent is not available for the JWT grant   since the JWT grant is used by autonomous  applications, where user is often not present. For JWT grant, an 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 feasible. DocuSign time provides  three options for JWT out-of-band consent,   administrative consent, individual  consent, and ISV administrative consent. This video discusses administrative consent  for the JWT grant. A future video will   discuss individual consent. ISV administrative  consent is required if an ISV application whose   integration key is managed by the ISV wants to use  administrative consent for users on your account.   More information on this consent  flow is listed in the show notes. Individual consent can always be used since it  can be used with any type of DocuSign account.   Many ISVs uses individual  consent since all DocuSign   customers can use it. I'll discuss ISV  issues more at the end of this video. If you've received the  consent_required error, well,   first thing is congratulations. Receiving  this error when you're using the OAuth JWT   grant flow indicates that your application  is creating a 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. Administrative consent is the  best JWT consent experience   since your users don't need to do anything. But  administrative consent has several requirements.   Your account needs the access management with  SSO also feature. SSO itself is optional. Your email DNS domain must be claimed.   Note that consent is only given to your users  whose email addresses match a claimed domain.   And your application's integration key must be  managed by an account within the organization. There are five steps for using administrative  consent, checking availability of the access   management feature; setting up your  organization; claiming your email domain;   granting administrative consent; and testing.  Step one is to check that your account has   the access management with SSO feature. This  feature's included with some DocuSign plans   and is optional for others. You do not need to  implement SSO. The feature can be requested for   developer accounts by contacting customer  support. See the show notes for details....