IBM Support

Enabling the communication protocal TLSv1.2 in Bridgeserver (LWAS-MIS profile) InfoSphere Metadata Asset Manager

Education


Abstract

Enabling the communication protocol TLSv1.2 to have a handshake with the ApplicationServer requries some configuration steps with IMAM - bridge server

Content

Following steps need to be added to server.xml in WAS Liberty for MIS profile on which the IMAM bridges are hosted.

in <WAS Liberty installDir>/usr/servers/mis/server.xml.



<ssl id="defaultSSLSettings"
clientAuthenticationSupported="true"
clientAuthentication="true"
securityLevel="HIGH"
serverKeyAlias="${mis.server.key.alias}"
sslProtocol="TLSv1.2"
keyStoreRef="mis-keystore" trustStoreRef="mis-truststore"/>

<ssl id="controllerConnectionConfig"
sslProtocol="TLSv1.2"/>

<ssl id="memberConnectionConfig"
sslProtocol="TLSv1.2"/>

Add following line in <WAS LIbertyInstallDir>/etc/server.env
JVM_ARGS=-Dhttps.protocols=TLSv1.2

Then restart the WAS Profile or service.

Original Publication Date

23 November 2016

[{"Product":{"code":"SSZJPZ","label":"IBM InfoSphere Information Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"IBM InfoSphere Metadata Asset Manager","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"11.5.0.1","Edition":"All Editions","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 June 2018

UID

swg27049121