APAR status
Closed as program error.
Error description
While Creating Trading Partner using the IBM Sterling B2B Integrator APIs as Listening Consumer over custom protocol, the remote server's password gets corrupted. So, the BP fails to authenticate to the remote partner's server during file routing.
Local fix
None STRRTC 539875 KK/KK
Problem summary
Users Affected: All Problem Description: Remote Password gets corrupt for trading partner created using IBM Sterling B2B Integrator APIs over custom protocol. Platforms Affected: All
Problem conclusion
Resolution Summary: The issue is due to key being used while obscuring password (at the time of password creation) and un-obscuring password (while attempting to connect to remote server through Begin Session Service) are different.So there is a modification where Extension name which has password that has to be encrypted in JSON should be passed as "ExtensionName+ _ENCRYPTED" as below, ExtensionName_ENCRYPTED:password ex:IBM_Rpwd_ENCRYPTED:password123 Delivered In: 5020602_5 5020603_3
Temporary fix
Comments
APAR Information
APAR number
IT20863
Reported component name
STR B2B INTEGRA
Reported component ID
5725D0600
Reported release
520
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-05
Closed date
2017-09-25
Last modified date
2017-11-06
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
STR B2B INTEGRA
Fixed component ID
5725D0600
Applicable component levels
R526 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
06 November 2017