Skip to Content
Jul 10, 2008 at 09:16 PM

Client Auth and SSL with Seeburger AS2 adapter


Hello All,

We are using the Seeburger AS2 adapter in our landscape and I am in the process of setting the same up and have made quite some progress in all my issues.

and I hope that you will be able to help me out.

1. Server SSL on Receiver AS2 adapter

I am sending a message from XI using the Receiver AS2 adapter to my AS2 test tool using Server SSL.

This is working perfectly fine. In my AS2 adapter I have selected HTTPS as the protocol and the message goes via SSL to the target test tool, is processed and the MDN comes back to XI perfectly.

The issue here is :

Irrespective of what is provided in the Server Certificate ( Keystore) , the message goes to my target test tool. I even left this field blank with no certificate entry and still the SSL connection was established and the message went to the target system.

Is there no validation that XI does here? I am lost what is the use of this entry Server Certificate if XI blindly accepts all SSL connections.

I am using a Decentral Adapter Engine with LoadBalancer.

2. Client Auth on Receiver AS2 Adapter

I tried to perform Client Authentication by proving my Server's private key in the AS2 adapter. The corresponding public key is loaded in my partner's Keystore.

XI error's with the error "SSL handshake failed - Bad Certificate" .

I am not sure why XI is erroring out here and I have a feeling that I have misunderstood the use of the fields in the AS2 adapter,

Server Certificate ( Keystore) and Private Key for Client Authentication.

Has anyone tried this? If further details are needed, I will be able to furnish the same.