IBM Support

PI88896: OIDC RP REFRESHED ACCESS_TOKEN IS NOT PUT INTO SUBJECT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If an OIDC access_token is refreshed by the WebSphere
    traditional OpenId Connect Relying Party (OIDC RP) TAI, the
    new access_token is not placed into the WebSphere Subject.
    

Local fix

  • Disable the authentication cache
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  OpenID Connect Relying Party                *
    ****************************************************************
    * PROBLEM DESCRIPTION: OIDC RP WebSphere Subject may not       *
    *                      contain current access_token            *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack or interim fix that      *
    *                  includes this APAR.                         *
    ****************************************************************
    In the authorization code flow, after the initial login, if
    the OpenID Connect Relying Party (RP) obtains a new access
    token (refresh) from the OpenID Provider (OP), the access token
    on the WebSphere Subject is not updated.
    The OIDC RP will need to refresh the access token if the
    access_token lifetime is shorter than that of the id_token.
    

Problem conclusion

  • The OIDC RP is updated to ensure that the active access token
    is in the WebSphere Subject.
    
    Since this functionality relies on custom cache keys, the OIDC
    property includeCustomCacheKeyInSubject must be set to true
    (the default).
    
    The OIDC RP uses the access token stored in its private cache,
    not the one stored in the WebSphere Subject.  Because of this,
    this issue only affects applications that are attempting to
    retrieve the access token from the WebSphere Subject.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.15, 8.5.5.14, and 9.0.0.8.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI88896

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-16

  • Closed date

    2018-01-24

  • Last modified date

    2018-01-24

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021