Enforcing Policy Server TLS1.2 handshake to LDAP Policy, User Stores
search cancel

Enforcing Policy Server TLS1.2 handshake to LDAP Policy, User Stores


Article ID: 189441


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) SITEMINDER



When running a Policy Server, how could the usage of TLSv1.2 be enforced when the connection to the backend LDAP Policy or User Stores?

How to enable SSL to debug logs too when connecting to this LDAP Directory?




Policy Server 12.8SP3 on RedHat 6;
Policy Store on LDAP ODSEE 11gR2;




At first glance, in an SSL handshake, the version of SSL is chosen by the server. In the case of the Policy Server connecting to the LDAP User Store, the LDAP User Store is the server and Policy Server is the client.

So the Policy Server will tell the LDAP User Store which versions of TLS it can handle, in the case of 12.8SP3, TLSv1.0, TLSv1.1, and TLSv1.2.

Then the LDAP User Directory will select the version and send the certificate (1):

The exact steps within a TLS handshake will vary depending upon the
kind of key exchange algorithm used and the cipher suites supported by
both sides. The RSA key exchange algorithm is used most often. It goes
as follows:

The 'client hello' message: The client initiates the handshake by
sending a "hello" message to the server. The message will include
which TLS version the client supports, the cipher suites supported,
and a string of random bytes known as the "client random."

The 'server hello' message: In reply to the client hello message, the
server sends a message containing the server's SSL certificate, the
server's chosen cipher suite, and the "server random," another random
string of bytes that's generated by the server.

Usually, the Server will use the highest version that the Client supports. To ensure that no connection will be done outside TLSv1.2, configure the Server (LDAP Server) to only support TLSv1.2. This might hurt compatibility with other software that doesn't support it.

To see which protocol is supported by the LDAP ODSEE version, run the openssl command as described in this Oracle document (2):

$ openssl s_client -tls1_2 -connect <HOST2>:<SSL_PORT2>

Running network traces on the Policy Server will help. The TLS packets exchanged between the Policy Server and the LDAP User Directory will show the version of TLS.


Additional Information



    What Happens in a TLS Handshake? | SSL Handshake


    ODSEE - What Versions of SSL and TLS are Supported by the Latest Version of the Directory Server (Doc ID 2047989.1)