@VENKATESH GUDEENTI Can you please remove https and use http in the redirect URI and also turn off TLS/SSL from service package of DocuSignService in Pega (see below)
@VENKATESH GUDEENTI Can you please try this outside Pega via PostMan to connect to DocuSign API to post an envelope? error indicates it has to do with credentials, may be there is some space at the end which is causing this.
@uashok93 Hi Ashok, Appreciate your reply. May I know how did you get alphanumeric username to set in pySetEnvelopeCredentials. I’m currently using the docusign login email address as username.
@VENKATESH GUDEENTI Seems like Docusign has advanced a lot . Did you try to create a Developer account for Docusign . Beacuse Now only with Developer account we can actually create an API key .
@uashok93 Yes Ashok, We need to take user name from Settings → Integration → Apps and Keys → User ID,
and password from User initials (Right top corner) → Manage Profile → Privacy and Security → Additional Security → App passwords → Generate app password.
With the above credentials, I managed to make a successful integration with DocuSign with 201 response.
@KOMARINA Alright, I managed to find the rootcause, The issue is with base url in pyDocusignBaseURL application setting. I changed the url from “https://demo.docusign.net” to “demo.docusign.net”. Because, Pega is already having “https://” in resource path of connect rest rule(pxSendNewEnvelope).
with that - moved to next step. Now the latest error is - 401, One or both of Username and Password are invalid.
But, I’m sure credentials are correct and I’m able to login.