APAR status
Closed as program error.
Error description
Turns out, neither native nor third-party OAuth providers, security definitions/schemas, and security requirements require ANY scopes to be configured. This is the case for BOTH OpenAPI 2.x and 3.x. The wording was ambiguous in v2.x, and was later clarified in v3.x API request is failing when they configure a security requirement with no scope. This is not validated on the API Connect UI, so when the configuration is processed on the Gateway, it fails. The failure is not propagated back to API Connect, so the user might believe the configuration they were using was valid.
Local fix
Problem summary
APIC scope handling regression
Problem conclusion
Fix is available in 10.0.1.14, 10.5.0.6 and 10.5.1 For a list of the latest fix packs available, please see: https://www.ibm.com/support/pages/node/83105
Temporary fix
Comments
APAR Information
APAR number
IT43730
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
A0X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-05-10
Closed date
2023-06-08
Last modified date
2023-06-08
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
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateways"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
09 June 2023