IBM Support

Authentication-failed for inbound AS2 message; verification failed: Expected signer info not found

Troubleshooting


Problem

Authentication-failed for inbound AS2 message; verification failed: Expected signer info not found

Symptom

After updating trading partner profile with a new AS2 certificate and receiving an AS2 data, EDIINT Pipeline Parse step completed with error and the Advanced Status shows Authentication-failed message.

Same message also shows in the Status Report and Process Data info.

Turning on logging for EDIINT.log (Operations > System > Logs > List and Go! > click the paper/pencil symbol besides EDIINT > select on > Save), asking trading partner to send another data, user noticed another error message indicating

verification failed: Expected signer info not found

Searching through Pipeline.log, user also sees the same Expected signer info not found message.

Information from Pipeline.log also shows that GIS/SI is expecting a certificate used by trading partner to sign the data that was sent over to be encrypted with a certain serial number as per trading partner AS2 setting;

while some other certificate's serial number was found.  These serial numbers are in hex mode.  One can normally see the serial number in hex mode when double clicking on trading partner's digital certificate and click Details tab.

Error Message

1.  Authentication-failed

2.  verification failed: Expected signer info not found

[{"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Historical Number

NFX10059

Document Information

Modified date:
14 November 2019

UID

swg21558373