When the Service Managerserver acts as a TLS/SSL client, it uses OpenSSL to connect to the Directory Services server via the secure LDAP protocol.

To enforce the TLS 1.2 protocol, configure the following parameter in the sm.ini file: As of Service Manager 9.41, the Service Manager server uses TLS 1.2 by default (TLS 1.0 and TLS 1.1 are also supported).

In this scenario, the Service Manager server is acting as a TLS/SSL server. The Service Manager server uses Java to securely manage and connect incoming client requests that use TLS and SSL protocols. As such, HPE recommends that you consult the vendor of your browser and third-party web application server (such as IBM Websphere, Oracle WebLogic, and Apache Tomcat) for information about how to configure TLS 1.2.Īs of Service Manager 9.41, the web tier, Mobility client and Windows client use TLS 1.2 by default. HPE does not provide the software that hosts the Service Manager web tier, Mobility client, or SRC products and it is this software that controls the specific TLS/SSL protocols that are used. Depending on the third-party web application server, these connections default to the highest supported version of the TLS/SSL protocol.

Examples of client requests include requests that originate from web browsers that are running on end-user’s workstations. When the Service Manager web tier, the Mobility client, and SRC act as TLS/SSL servers, they use the Oracle or IBM Java virtual machine (JVM) that is required by your third-party web applications server to securely manage and connect incoming client requests that use TLS or SSL protocols.

Administer > System Security > TLS 1.2 Support and Configuration TLS 1.2 Support and Configuration

Test tls 1.2 support