APAR status
Closed as program error.
Error description
The AS1 Protocol fails to sign the MDN.
Local fix
Problem summary
The XB user who is adopting B2B Gateway service to receive B2B documents over AS1 with MDN requested by external partner. The pre-condition is that the B2B Gateway service processes an inbound message over AS1 (AS1 Frontside Handler) and the Business IDs are extracted by the Email From: and To: headers rather than the Subject header. If the message sender (ie., the external partner) requests for a signed MDN, an error of "Failed to sign MDN from business ID foo@bar" occurs because of inability to get the Identity Credential for signing the AS1 MDN.
Problem conclusion
The fix is available on 3.8.2.14, 4.0.1.12, 4.0.2.8 and 5.0.0.1.
Temporary fix
Comments
APAR Information
APAR number
IC83835
Reported component name
DTAPWR B2B APL
Reported component ID
DP905XB62
Reported release
402
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-30
Closed date
2012-07-18
Last modified date
2012-08-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DTAPWR B2B APL
Fixed component ID
DP905XB62
Applicable component levels
R401 PSY
UP
R402 PSY
UP
R500 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSHTED","label":"WebSphere DataPower B2B Appliance XB62"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.0.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 August 2012