How to use Keystore (Truststore) in the Connect REST wizard
I am trying to run a Connect REST wizard to generate integration rules to connect to an external system. External REST API, "Authenticate", requires username and password in the JSON Body request, and if they are valid ones, external system will return Bearer Token for other APIs authentication.
Here is how I make a POST request using Postman, and it works completely fine.
Now I want to do the same in Pega Platform. Below is a screenshot of Connect REST wizard. I am configuring the same way as Postman.
However, I get below error (SSLHandshakeException).
This is because I am not using Data-Admin-Security-Keystore anywhere in this wizard. Below is prior screen but I don't see any field where I can specify Keystore (Truststore). If I create Connect REST rule instance by myself (without using wizard), I can specify Keystore in the rule..
I want to use wizard so Pega Platform will analyze the response and generate a bunch of properties and classes automatically under Int class.
Thanks for the info. I am using Tomcat and yes I thought about it, but I heard that keystore/truststore at PRPC level is better practice than application server level. Do you agree with that?
If that is agreed, I would still want to do it at PRPC level, and also still want to use the wizard (I believe unless we use wizard, there is no way that PRPC generates a bunch of integration rules like Int classes and data page for you, automatically. Am I correct?) How come Connect REST wizard does not have keystore/truststore field? Is there any meaning for this, or is it just a specification?
If you want response structure (Properties/ Data model, Int classess, stream/parse rules .. etc) to be created by wizard you can use the sample json structure in response, which will build you the required rules.
Oh I see... I never paid attention to the file upload functionality in the test connection pop up but that can be used like this use case, when PRPC is not able to reach out to the external system! This way, we can still use the wizard, and also create properties based upon the sample JSON response file. After Connect REST rule instance gets created, I should be able to manually open it and save keystore/truststore there by myself.
In the meantime, I will also try importing PKCS12 file into JVM for practice as the second approach.