Skip to main content
Active Voice
December 24, 2024
Solved

When to use JWT Grant

  • December 24, 2024
  • 3 replies
  • 309 views
JWT Grant

I am new to Docusing and was going through the documentation. I stumbled upon the Authorization Grant of the Platform 101 docs, and read the above excerpt. Can anyone clarify what does this mean 

If you use a single login for all users in your integration, you should use JWT Grant

 

Using single login for all of the integration users mean what? Does that all follow the same login/signup method or the same credentials?

Best answer by JohnSantos

@versatilevats 

If your integration requires actions to be performed as individual DocuSign users (e.g., employees logging in with their own accounts for signing or sending documents), then you wouldn't use a single login. Instead, you'd implement the Authorization Code Grant flow, allowing each user to log in separately.

In the context of DocuSign, “using a single login for all of your integration users” means that you have one DocuSign user account (i.e., the same set of credentials) that your application uses to generate all access tokens for every user of your application. Rather than having each end-user authenticate separately with their own DocuSign account, your application acts on behalf of a single “system” user.

That is why DocuSign typically recommends JWT Grant (sometimes called “Service Integration”) if you want to manage only one DocuSign user account and use it for all of your application’s DocuSign operations.

In other words:

  • Single Login = a single DocuSign user/account.
  • Same Credentials = the integration uses the same email/password or authentication method (e.g., private RSA key for JWT) for all operations.

Whereas if you wanted each of your end users to have their own DocuSign account and authorize individually, you would use the OAuth “Authorization Code Grant” flow.

3 replies

JohnSantos
Guru
Guru
December 24, 2024

@versatilevats 

If your integration requires actions to be performed as individual DocuSign users (e.g., employees logging in with their own accounts for signing or sending documents), then you wouldn't use a single login. Instead, you'd implement the Authorization Code Grant flow, allowing each user to log in separately.

In the context of DocuSign, “using a single login for all of your integration users” means that you have one DocuSign user account (i.e., the same set of credentials) that your application uses to generate all access tokens for every user of your application. Rather than having each end-user authenticate separately with their own DocuSign account, your application acts on behalf of a single “system” user.

That is why DocuSign typically recommends JWT Grant (sometimes called “Service Integration”) if you want to manage only one DocuSign user account and use it for all of your application’s DocuSign operations.

In other words:

  • Single Login = a single DocuSign user/account.
  • Same Credentials = the integration uses the same email/password or authentication method (e.g., private RSA key for JWT) for all operations.

Whereas if you wanted each of your end users to have their own DocuSign account and authorize individually, you would use the OAuth “Authorization Code Grant” flow.

Welcome to the DocuSign Community! Your feedback is highly valued. If you find my response helpful, please give it a "Like" and consider marking it as the "Best Answer" to assist others with similar issues.
Active Voice
December 25, 2024

Thanks for the reply ​@JohnSantos. So, I will go with JWT Grant for my application.

Newcomer
July 30, 2026

Follow-up question on this….  If I wanted to use JWT so that my SVC account is authenticating the requests from another hosted web application, how does it allow embedded signing as individual users with the envelope?  Everytime I try to modify the config settings, the SVC acct is applied to the Signer_Name and Signer_Email.  I want both of those values to feed from information within the other web application.  Thanks!