DocuSign Integration Authentication Error

General
, , ,
1

“Connector is configured to use authentication, but the Authentication Profile value is empty”

I am trying DocuSign integration in community edition by following general implementation steps.

I have created DocuSign Account and done required configurations for authentication. In Dev I have added component and modified the Data transforms related to DocuSign (pyPrepareNewEnvelope and pyAssignRecipientsToEnvelope). After that I have created OAuth2.0 authentication profile using Keystore (used OpenSSL and created required certis).

I have verified DocuSign Connections and it is in CONNECTED status.

I cannot able to hit the DocuSign API. there are no requests are sent to it.

Screen Shot.png
Screen Shot.png1348×726 37 KB

i will attach document containing Screenshots and also the link i have followed.

guide link: How to connect to DocuSign | Support Center (pega.com)

Any comments and suggestions are really apricated.

Thank You

Error File.docx (661 KB)

2

@B Anurag I haven’t tried that myself, and I do not doubt the instructions that you followed.

I do have one suggestion, you can double check your config using these instructions: Configuring the DocuSign authentication (pega.com)

3

@PhilipShannon thank you for your response,

As you suggested I have checked the document you share and turns out the instructions are the same.

I think the Keystore Iam using for authentication is the problem, I have used OpenSSL to generate a PKCS12 file and used it in Keystore.

I have a question, does Pega 24.1 accept Self Signed Certificates? Iam using Community edition for this integration.

Thank You

4

@B Anurag It appears that Pega does not support the use of self-signed certificates for certain integrations. For example, in the context of SAML 2.0 configuration, it is mentioned that the rule engine allows only CA certificates and not self-signed certificates. This suggests that for secure integrations, Pega prefers certificates issued by a Certificate Authority (CA) to ensure optimized security

FDBK-114091 (Pega self signed certificate)

5

@MarijeSchillern Thank you for your response,

Yes, I think the same. I have tried to do the implementation in other new application but the results were the same. the is authentication always failing because of Self signed certificate. currently I can’t get CA certificate maybe I will try them in future.

Thank You