Question
1
Replies
446
Views
United Health Group
Posted: May 17, 2017
Last activity: May 17, 2017
Closed
Mutual SSL for Connect Rest Integration in PRPC- 7.1.6
As part of development project, we are trying to use Connect Rest to call an API through Mutual SSL. Since connect-rest rule form (V7.1.6) doesn’t provide options for trust store and keystore to implement Mutual SSL. What are the configuration changes required in PEGA and in Application server? Is there any option available at the Connect-Rest rule level for configuring the keystore .
Steps to Reproduce
1.Create a REST connector and configure using SSL secured REST service
2.Invoke Connect-REST rule from the activity
2.Invoke Connect-REST rule from the activity
Error Message
<defaultResponse_POST>{
"ErrorID":"314f9bc6-34b8-4814-93de-385c2af9f8c0",
"ErrorCode":"2.1",
"ErrorMessage":"Error",
"Advice":"If problem persists, please contact API team"
}</defaultResponse_POST>
"ErrorID":"314f9bc6-34b8-4814-93de-385c2af9f8c0",
"ErrorCode":"2.1",
"ErrorMessage":"Error",
"Advice":"If problem persists, please contact API team"
}</defaultResponse_POST>
As per API guidelines, No certificate is being passed with API request. Must be fixed in consuming application.
what application server are you using? Check some of the pointers for tomcat if that is case:
https://pdn.pega.com/community/pega-product-support/question/implement-2-way-ssl-rest-integration