6.03 installation with mutal authentication
in our clm 6.0.3 setup plan, our applications (JTS,CCM,QM,RM,DNG,DM,DCC,LQE, JRS,RELM) need to be hosted in 9 different linux servers with bundled liberty profile.And also we have one IHS server in front of them.
Accepted answer
IHS only needs to know about the Liberty profiles self signed certificates, as when the applications hosted in the Liberty profiles contact each other, it is through the public side of IHS, which has the validated certificate from a root CA provider.
6 other answers
Which document are you following? I guess this one?
https://jazz.net/wiki/bin/view/Deployment/CLMDistributedSetupUsingLibertyProfile
Since you have IHS as a reverse proxy, there should be no traffic between any two of the Liberty profiles. So you only need to care about the SSL handshake between IHS and each Liberty profile. Depending on your company's security policy, you can use self-signed SSL certificates for the Liberty profiles. In other words, you only need to request a CA-signed certificate for IHS.
Hi, Donald,
Comments
Exporting/importing an SSL certificate should be the same regardless which truststore you are dealing with. What you need to care about is which certificate you import. The end result should be like this - a client (say, IHS) sends a request to the server (say, Liberty) to establish an SSL connection, the server returns a certificate, the client checks the certificate and verifies it's in its truststore (i.e. the certificate is trusted), and the client proceeds with the connection. It is also true if you make Liberty as the client and IHS as the server.
If this is a duplicate of https://jazz.net/forum/questions/250037/clm-603-installation-with-ssl-mutual-authentication-between-applications-as-well-as-dbs let me know which one you want to keep so can close the other one.
Hi Ralph,
Hi Donald,
The example was well clear .Thanks!
But again have one query that, by considering the scenario as follow.
1st communication):-Considering IHS as client and liberty profile as server.
When establish an SSL connection, the server returns a certificate, the client (IHS) checks the certificate and verifies it's in its truststore (i.e. the certificate is trusted) . How to make this trusting by details. which approach i can take care . I am using IKEYMAN.
a) Liberty profiles already have default key sore file. can we directly copy this and import to IHS kdb file ? will it make it trusted here ?
b) or do we need extract the certificates from Liberty profiles default keystore and copy and import the certificate to ihskdb file ?
Both are same?..
and one more clarification needed as, We dont have a trust file in IHS, So same .kdb file will act as the trust store here?
2) Considering Liberty to IHS communication.
For making IHS certificates trusted in Liberty profile trust store. What approach we can take here ?
can we follow the same way as extracting the certificate frrom IHS servers kdb file and import in liberty server keystore.
Regards
vowner
Comments
The operation you need is export/import, not copy. You export the SSL certificate from the server's keystore, then import it into the client's truststore (can be the same as the keystore). As long as you identify the client and server, it does not matter whether it is IHS or Liberty.
Hi Donald,
If you follow the document that I posted earlier, there is no "export" or "extract" involved. It says "Copy the certificate keystore from each liberty profile to Server1 hosting IHS", which means to take the keystore file as is.
Hi Donald,
Also I couldn't find any document which is posted by you as you mentioned in previous comment,
Any advise please
I was referring to this document:
https://jazz.net/wiki/bin/view/Deployment/CLMDistributedSetupUsingLibertyProfile
any suggestion here
Hi Donald,
But here its not describing anything about how to make the mutual ssl authentication with the IHS,
I meant in liberty server what need to do make mutual authentication with IHS, in the given link its describing only about IHS side and no configuration steps from liberty side..