APAR status
Closed as program error.
Error description
Modify LDAP failed with 500 error if UR is used in API User Registry in Catalog
Local fix
Once the ldap has been created and associated with any Provider organizations in any catalog, the issue can be observed when using Cloud Manager UI to edit any field in the LDAP As a temporary fix, remove all user registry association in all Provider Organization and edit the required field(s). Once edit works, can add again.
Problem summary
Modifying an LDAP registry in Cloud admin may fail with a 500 error if the user registry is used in Catalog API User Registry. This may be observed in the api connect logs: Highlighting the specific error: "message":"Error decoding JSON value for configuration: Expected a UTF-8 string, but got a LinkedHashMa
Problem conclusion
The product is updated in 2018.4.1.15 to address the issue.
Temporary fix
Comments
APAR Information
APAR number
LI81489
Reported component name
API CONNECT ENT
Reported component ID
5725Z2201
Reported release
18X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-05-06
Closed date
2021-01-31
Last modified date
2021-01-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
API CONNECT ENT
Fixed component ID
5725Z2201
Applicable component levels
R18X PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18X","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 September 2021