ECC -> PO -> AS2
This blog is about my experience about how I understood the existing blogs for setting up AS2 connection and what I actually did to setup for one of my client. We have so many blogs and standard docs to talk about it. But I am going to share my experience on how I was confused and then got a clear picture of it.
Many thanks to the 4 blogs of Dimitri Sannen that explains about the free to use AS2 software from mendelson.
There are some points you need to know before using the free AS2 software.
1. When You use this software to setup a test AS2 receiver channel. You should use the AS2 ID mentioned in the blog any different id didnt work for me.
2. The key1 mentioned in the blog is used to sign the message, it needs to be added to your NWA keystore. its a PKCS12 file it will require a password to open it which by default is “test”. To download key1 and key2 click here mendelson AS2 solution
3. The Key2 is an actual public certificate of the mendelson, which was added to NWA keystore and used it to encrypt the message.
4. The Key1 created so much confusion for me. what I received from my AS2 partner for AS2 communication did not have any key files of this sort. So I was about to ask them to send a private key over to me.
5. In my real scenario to setup AS2 communication, for signing I used my own public certificate from NWA and private key from NWA, and we shared our certificate to the AS2 partner for verification purposes. This contradicts with how the mendelson setup was.
6. Using a self signed certificate in NWA keystore should work as well.
7. To create yourself a self signed cert you can use keystore explorer. its a free software available to generate your own CSR, CER or PKCS12 etc.
Note: For signing the message on the AS2 channel, You always have to use your own public cert and private key from your NWA keystore.
And for encryption you always use the AS2 partners public certificate.