IBM Support

IT45298: OAUTH CACHE UPDATES EXISTING ENTRIES RATHER THAN CREATE NEW ENTRIES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When using Third-party in-memory option, we update existing
    cache entries that have the same key instead of adding new ones,
    due to the OAuth introspection specification's implication that
    an introspect call will return the same response for the same
    valid token.
    
    
    This ÅPAR fixes that problem and clears the cache before
    creating a new cache key entry.
    

Local fix

Problem summary

  • Make sure the new data is cached when key already exists.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT45298

  • Reported component name

    DATAPOWER

  • Reported component ID

    DP1234567

  • Reported release

    A0X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-01-18

  • Closed date

    2024-04-17

  • Last modified date

    2024-04-23

  • 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":"BU048","label":"IBM Software"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateways"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
23 April 2024