You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add PKCE support to the SDK, and here are two different ways to do so:
Abstract away PKCE by adding an initialization option enablePKCE: true to the ApiClient constructor, where code_challenge and code_verifier are added to requests under the hood.
Add optional parameters to authentication functions to allow us to send our own code_challenge and code_verifier in each relevant call.
The text was updated successfully, but these errors were encountered:
DocuSign does not support Authorization Code Grant in our SDKs since it is webstack dependent. Instead, a generic (not DocuSign specific) OAuth library should always be used. Node for example is usually used with Passport. Some support PKCE, others do not.
It would be acceptable for an additional optional parameter object to requestJWTUserToken (and ACG equivalent) where we can fill in the code_challenge and code_verifier.
DocuSign now supports PKCE since March 2023 https://www.docusign.com/blog/developers/docusign-adds-support-pkce.
Unfortunately there is no way to make use of PKCE using the SDK, and I have not found workarounds.
We should add PKCE support to the SDK, and here are two different ways to do so:
enablePKCE: true
to theApiClient
constructor, wherecode_challenge
andcode_verifier
are added to requests under the hood.code_challenge
andcode_verifier
in each relevant call.The text was updated successfully, but these errors were encountered: