Describe the bug
The correct outboundConnection is not selected when multiple outbound connections are configured under one ssl id.
Steps to Reproduce
- Create multiple outboundConnections under one ssl id.
- Make one of the outbound call
- Liberty seems to concatinate all aliases to lookup and fail to find the ssl configuration.
<ssl id="mySSL" keyStoreRef="myKeyStore" trustStoreRef="myTrustStore" securityLevel="HIGH" sslProtocol="TLSv1.2" verifyHostname="false" trustDefaultCerts="true">
<outboundConnection host="test1.ibm.com" port="50001" clientCertificate="OUTBOUND_CERT1"/>
<outboundConnection host="test2.ibm.com" port="50002" clientCertificate="OUTBOUND_CERT2"/>
<outboundConnection host="test3.ibm.com" port="50003" clientCertificate="OUTBOUND_CERT3"/>
</ssl>
Expected behavior
The correct ssl configuration is selected.
Diagnostic information:
- OpenLiberty Version: [e.g. 21.0.0.8 - 21.0.0.10]
- Affected feature(s) [e.g. mpHealth-3.0]
- Java Version: [i.e. full output of
java -version]
- server.xml configuration (WITHOUT sensitive information like passwords)
- If it would be useful, upload the messages.log file found in
$WLP_OUTPUT_DIR/messages.log
Additional context
Add any other context about the problem here.
Describe the bug
The correct outboundConnection is not selected when multiple outbound connections are configured under one ssl id.
Steps to Reproduce
Expected behavior
The correct ssl configuration is selected.
Diagnostic information:
java -version]$WLP_OUTPUT_DIR/messages.logAdditional context
Add any other context about the problem here.