10-05-23 05:25 PM
Hi team, I am getting a protocol error while accessing through blue prism API but I am able to access it through Postman.
Can someone else help me to resolve this error?
Currently, I am using blue prism suggested Docusign VBO and attached here it for reference.
Thanks,
Srikanth
16-05-23 05:33 PM
Hi Srikanth,
Thank you for being a SS&C Blue Prism customer and for using Blue Prism.
Can we check a couple of things regarding to your issue?
In Postman how do the headers compare to the headers you have in Blue Prism? I am aware that there can be confusion over the Content-Type header.
If you can come back to me with what you have that would help for a start.
Once again, thank you for using Blue Prism.
regards
17-05-23 12:10 PM
Thanks, Geoff for your response.
Here are the details of the header that I am using
And also the authentication details are below:
............................................................
Thanks,
Srikanth
17-05-23 12:43 PM
Hi Srikanth,
Thanks for this. Could you also supply the similar information for what you have working in Postman, so we might compare them and see what is different?
thanks
17-05-23 06:03 PM
Hi Geoff, below are the Header details I used in Postman.
Check the below URL for Postman collection
https://developers.docusign.com/tools/postman/
17-05-23 06:09 PM
Hi Srikanth,
Could you try replacing the Content-Type header in Blue Prism with the value you have in postman? So, replace the Application/json in the Blue Prism header with the application/x-www-form-urlencoded that you have in Postman?
See how that goes and report back to me.
regards
18-05-23 01:15 PM
Hi Geoff, Tried with the above-suggested header details and got the same error.
18-05-23 01:23 PM
Hi Srikanth,
It would be useful now to see what you have configured for the Docusign Credentials. Given the error, something is different in Blue Prism to what you have in Postman, we just need to find what that difference(s) is/are.
regards
18-05-23 03:58 PM
Srikanth,
Having now managed to get time to try out and replicate the issue you have I did the following:
1. I have created an App inside of docusign. In the developer sandbox and i have created a single template in the app.
2. I have followed the user guide.
3. I am using the List Templates action on the Docusign Wrapper Object. The Account ID I have used is the API Account ID.
4. In the Common Authentication - Subject I am using the API Account ID.
5. In the Docusign Credential I am using the integration key as the issuer and the private key is PKCS
#8 created as shown in the user guide.
As I have only 1 template created in my application, it is now displayed in my Templates collection.
18-05-23 06:54 PM
Hi Geoff, tried a couple of times with the same steps but seeing the same protocol error. I am not sure where I went wrong while following the user guide. Could you please check and verify the below steps.
Redirect URL landing page:
Captured the API Account ID & Integration Key:
Authentication settings:
And used the Integration key as the issuer name and the private key is PKCS #8