We have a problem in PROD with our new Trading Partner (TP), lets call it “A”.
We are able to send EDIINT message to TP “A” successfully. But when TP “A” are trying to send to us, it is got error “processed/error: authentication-failed”.
The other TP are going fine. When we tested this TP in DEV, it was went well.
We have load TP certificate in MWS for
Sign/Verify
Encrypt/Decrypt
SSL
We have load TP certificate in IS Server Truststore List also.
We are using webMethods 10.3.
The guy from TP “A” that support the system said that he loaded the certificates correctly on his side.
He shared this setting as below:
Encryption Algorithm: 3DES
Signature Algorithm: SHA1
SSLEnabledProtocols: TLSv1.0, TLSv1.1 & TLSv1.2
Send Message Security: Sign and Encrypt
Send Message Security: Sign & Encrypt
MDN : Signed & Synchronous
I found there is nothing wrong with their setting, but somehow the transactions from them still got error.
I assumed there is no problem with our certificate since it is working well with other TPs.
And because the error is too simple to troubleshoot,
I have enabled for IS logging no:
0006 (Server SSL Interface)
0007 (Authorization)
0009 (Certificate)
0012 (Authentication)
But nothing is captured related to above error.
Any idea which logging that I need to enable so it will help me to troubleshoot?
Or any idea on how to solve this issue?
Please take a look at this EDIINT from MWS. If there is no payload on the Content tab like below. That means company A uses the wrong certificate to encrypt the payload and you can not decrypt it.
I am totally agree with you may be the TP “A” uses the wrong certificate, but the question is how to prove to them that they are using the wrong certificate?
They insisted that they installed the certificate correctly.
That’s why i am trying to increase the logging level. But still not able to capture meaningful error to troubleshoot.
I will try to increase all under EDI_Module, hopefully it will works.
Thanks for the information provided. Really helpful.
Anyway, finally we managed to sort out the problem.
TP “A” was putting “ Content-Type: text/plain ” in EDIINT setting which is causing the issue.
Once they changed to “ Content-Type: application/EDIFACT ”, the transmission is successfully received.
be careful with these file extension as they do not always indicate the real file format.
I.e. Windows is proposing cer extension for both formats (plain text/CER and binary/DER).
You can check this by opening the file in doubt in a text editor.
Plain text looks somewhat human readable and has two lines “BEGIN CERTIFICATE” and “END CERTIFICATE” in it.
Binary format doesn´t look readable to humans.
Hi Fanny,
I am glad to hear good news. I made a test with “ Content-Type: text/plain” and got a positive MDN from a partner like below. I doubt that “ Content-Type: text/plain ” in the EDIINT setting which is causing the issue “authentication-failed”.