Question
Dynamically refer TrustStore/KeyStore in a connect Rest rule
Hi,
For some of the services in my application, we are using SSL and a trust store but that changes for different environments. Is there any way we can achieve this?
Solutions Tried:
1) Referring my DCR data page property and creating multiple TrustStores with different names
The trust store field on the ConnectRest rule only takes the Trust Store rule name.
2) Tried to send it in a param.
Same issue
***Moderator Edit-Vidyaranjan: Updated Title as per comment***
Like the end point URL is passed from a data page which will be fetched from system setting to deal with different end points for different environments, I am looking for dynamically referencing to a trust store which will be changed based on the environment. I only way I can achieve without editing the connect Soap in each environment is using a trust store and editing that instance in each environment with different keys. Hope you understood the requirement.
Hi Goutham
The recommended way is to keep SSL certificate at Application server level. As per your requirement you have different service/end points (SSL certificate) for each environment. Recommendation is store SSL certificate at app server(e.g. weblogic) level. In this way you no need to maintain SSL certificate/trust store for each environment.
Hope this helps.
Hi Goutham
The recommended way is to keep SSL certificate at Application server level. As per your requirement you have different service/end points (SSL certificate) for each environment. Recommendation is to store SSL certificate at app server(e.g. weblogic) level. In this way you no need to maintain SSL certificate/trust store for each environment.
Hope this helps.
If you're on P7.3.1, refer to HFix-42785. The hotfix corrects an issue where you cannot externally reference a trust store. This is relevant to your case where you can define & host a physical jks on your target environment, and have your truststore rule reference that jks via local file path url (ex. ./keystores/mykeystore.jks)
Alternatively, you can define a keystore definition via a function. Then you can put whatever logic you want to determine which physical keystore to use.
Hi Goutham,
The use case is not clear and what exactly are you looking for. A connect rest rule only connects to a single service so why would you need multiple trust stores.
If what I understand is correct from the above post, you should be better off by adding different certificates to the truststore defined at application server level. Then, depending on the service requirements, the corresponding trust store will be picked automatically.