Review and adjust the "DocuSign" integration for EasyCLA about easycla HOT 4 CLOSED

@mlehotskylf
I have done my investigation about new authentication strategy, and i found there are two authentication flow for docusign as below:

1. Authorization Code Grant : It is centered on interactions between the user and the identity server via the browser, the SDK is not used.
2. JSON Web Tokens: It is used with sdk, Also there are two JWT grant method:
   • request_jwt_user_token: that will represent a specific user, which will handle all rest API operations
   • request_jwt_application_token: that will represent the application itself (not a user). This will handle all admin operations.

According to me, we need to follow JWT token with user_token for our application usecase.
Also the sdk library we are using currently pydocusign is deprecated and new authentication strategy is not supported with it so we need to replace it with docusign-esign, which cause update the whole docusign integration.

from easycla.

Story implementation will be tracked on the below issue, So moving status Done

• Upgrade DocuSign Integration for EasyCLA #4002

from easycla.

@nickmango, Kindly review the below issue

1. request-individual-signature API is failed with 502 status on ICLA sign-in process
2. CLA System is not able to support your request that appears on CCLA sign-in process
   Refer screenshot for more details
   
   

from easycla.

We switched to Golang instead of Python so this ticket in no longer relevant, so closing. Ticket related to Golang is here: #4002

from easycla.