Skip to content

Liberty Fails to Select Correct SSL Configuration When Multiple OutboundConnections Are Defined #34391

@una-tapa

Description

@una-tapa

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.

Metadata

Metadata

Assignees

Labels

release bugThis bug is present in a released version of Open Liberty

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions