APAR status
Closed as program error.
Error description
When there are two or more similarly named OAuth clients DataPower might not locate the correct OAuth client information to handle the token that is generated. The end result is the token is rejected as not valid.
Local fix
Avoid similar names (such as client-01-abc and client-01) for OAuth clients in the same OAuth client group.
Problem summary
Affected are users adding an OAuth client to a group. If the a new client configuration changes to OAuth Group is not saved (Apply), then there is a small window, that during which another client with the same spelling at the beginning might be selected for handling the payload. For example, a new client with name oauth-client-abc is created, and added to the group, but the group information is not applied, or saved, then another client with name oauth-client-ab might be used instead.
Problem conclusion
Fix is available in 5.0.0.9 and 6.0.0.0. For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Temporary fix
Comments
APAR Information
APAR number
IC91815
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
500
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-04-23
Closed date
2013-07-23
Last modified date
2013-08-05
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
DATAPOWER
Fixed component ID
DP1234567
Applicable component levels
R500 PSY
UP
R600 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 February 2022