Skip to Content

PI 7.2 Seeburger AS2 adapter communication channel

In PI7.3 Seeburger AS2 adapter based communication channel, there are some differences in configuration comparing to PI7.1.

As I showed in the image of screenshot, anyone knows what does those parameters do?

In later Intergrated configuration, we also have chance to assign partner's certificate key and our own key. What's the difference of the 2 places where we assign the certificate key?

Key in communication channel

Key to be assigned in Integrated configuration

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Jul 21, 2016 at 04:03 AM

    Use Custom List for TrustedCAs

    By Default the Seeburger channel looks at the SAP PI TrustedCAs Keystore to have a SSL Trusted Connection. Any certificate that is signed by a TrustedCA is accepted by the Adapter.

    If you have a self Signed Certificate or would like to use a specific certificate, then you can use the Option Use Custom List for TrustedCAs and select the Keystore and the Certificate ( Public ) for the SSL Connection.

    It is recommended to use the CustomList for TrustedCAs only if you want to use Self Signed Certificate. Else use the Default PI Trusted CAs option

    Client KeyStore & Client Key

    In the Sender AS2 Channel, Client Keystore and Client Key is for Client Authentication. When I say Client Authentication, what I mean is that instead of a Basic Authentication ( user name / password ) or Anonymous, you impose that the Sender of the Message use a Client Authentication aka 2 Way SSL to do this. This should be the Partner Public Certificate.


    Sorry above was incorrect. Client Keystore and Client Key is required when you want to send the MDN back from PI and the Partner requires you to use Client Authentication. In such a case you need to provide your PI Private Key for Client Authentication here and then PI would use this to authenticate itself for the MDN.

    Partner for Authentication

    Partner For Authentication refers to the Partner Public Certificate for Verification of the Signature

    Own Key for Decryption

    Own Key for Decryption, refer to own Private Key to decrypt the mesage.

    Regards

    Bhavesh

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 21, 2016 at 12:54 PM

    You need to install your partner certificate on the NWA.and generate your own Public and private keys.

    Then you need to send to your partner your own public key and set the AS2 channels and Agreements:

    In the AS2 Sender channel choose your certificate Store values.

    In the AS2 Receiver choose the partner key select the Partner certificate provided to you.

    For your own certificate select it from the keystore as well.

    I prefer using a custom keystore and not the default just to keep everything nice and clean.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.