How to configure your B2B delivery channel to use a certain SSL certificate when transport protocol is securred and 2-way SSL is enabled
(Doc ID 2116217.1)
Last updated on MARCH 25, 2019
Applies to:Oracle SOA Suite - Version 220.127.116.11.8 and later
Information in this document applies to any platform.
Your B2B Engine must send a message to a remote partner over a secured protocol (HTTPS, FTPS). Remote partner has enabled 2-way SSL at their server side. B2B Engine is the "client" in this connection, and remote partner's B2B is the "server". When 2-way SSL is enabled, client must present its own certificate to server.
You have MULTIPLE SSL certificates in your keystore and you would like to use a certain SSL certificate for configuring this secured delivery channel with the trading partner.
Currently, there is no option to configure a certain certificate to be used for the SSL handshake when the transport protocol is secured. If there are multiple SSL certificates/identities in the B2B keystore, B2B will erratically pick one for presenting it during SSL handshake when 2-way SSL is enabled.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document