Secure communication with SSL

SSL connections require client-side authentication. webMethods B2B Integration uses the sender's profile to retrieve the certificate and private key for connecting to the receiver (the remote secure server).

The following table lists the possible communication sender-receiver scenarios and how webMethods B2B Integration uses the secure communication mechanism for each scenario:

Scenario	Secure communication mechanism that webMethods B2B Integration uses
webMethods B2B Integration finds a receiver-specific certificate set to use	The public certificate set along with the private key.
webMethods B2B Integration does not find a receiver-specific certificate to use	The default certificate set along with the private key specified in the sender’s profile.

SSL scenario with C1 as the primary SSL certificates

Here, C1 is the primary SSL certificate.

Step	Description
1	The enterprise sends a document to its business partner over HTTPS. It uses the private key from certificate C1.
2	The business partner's server authenticates the document by using the SSL certificate C1 configured on the server. Authentication is successful, and the transaction is complete.

SSL scenario with C2 as the primary SSL certificate

Here, C1 is the primary certificate. C2 is the SSL certificate.

Step	Description
1	The enterprise sends a document to its business partner over HTTPS. It uses the private key from certificate C1.
2	The business partner's server authenticates the document by using the SSL certificate C2 configured on the server. Authentication fails.
3	The enterprise sends an error message to the enterprise.
4	The enterprise switches the SSL certificate to C2.
5	The business partner resends the document to the enterprise over HTTPS.
6	Business partner authenticates the document by using the SSL certificate C2. Authentication is successful. The transaction is complete.