In order to achive a successful SSL connection you have to provide target server's certificates within a truststore file to the connector definition. But this approach seems to be hard to maintain. Generally test and production enviroment certificates are different. You might provide two different connector rule definitions and achive them dynamically but this time you have to maintain certificate changes (valid through dates etc.). With this approach you can't get the benefit of using Websphere Application server's trusts store where system administrators will manage a single point in system and they don't have to deal with details of PEGA where they have no idea about it. So the question is : is it possible for PEGA to use Websphere Trust Store instead of providingTruststore file? I tried it several times but I couldn't manage to make it work without providing key store file.
The version of Pega PRPC is 7.1.3.
***Edited by Moderator Marissa to update SR Details***
Pega should fall back to using the application server level trust store if there is no rules level trust store set. However, there is a bug for versions before 7.2.2 where this doesn't happen on Websphere. Since 7.1.3 is such an old version, your best option is to upgrade to 7.4, where this feature works out of the box. If you can't upgrade and this is a must-have feature, we might be able to port HFix-34470 to 7.1.3. If that's what you want, please open an SR and reference this thread.
thanks for your reply we also facing with the issue which restricts rest connector to use SSL protocol where we had to use TLS instead. I solved the problem by overriding pyInvokeRest activity which doesn't seem to be a clean solution. Can we also fix this issue within the version 7.1.3?