PI94538: OPENID CONNECT RELYING PARTY DOES NOT INVOKE THE REVOCATION ENDPOINT ON THE OP ON LOGOUT

PI96508: OIDC v1.05; OIDC RP may not connect to token endpoint due to SSL handshake failure
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
PH08804: OIDC v1.1.0; OIDC RP default identifiers are not available when customs are configured
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
PH13175: OIDC v1.2.0; OIDC RP tokens are not revoked when sessions are evicted from the cache
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
PH29099: OIDC v1.3.1; OIDC RP: ClassNotFoundException for JsonUtil$DupeKeyDisallowingLinkedHashMap
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
PH39666: OIDC v1.3.2; OIDC RP: Initial login might fail when the OIDC stateId contains special characters
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• The WebSphere traditional OpenID Connect (OIDC) Relying Party
  (RP) does not invoke the revocation endpoint on the OP during
  logout.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server users of   *
  *                  OpenID Connect                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: OpenID Connect logout does not revoke   *
  *                      tokens because no revocation URL can    *
  *                      be                                      *
  *                      configured                              *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack that contains this       *
  *                  APAR.                                       *
  ****************************************************************
  When performing a logout, the OpenID Connect (OIDC) Relying
  Party (RP) Trust Association Interceptor (TAI) provides no
  method to invoke the revocation endpoint on the OpenID
  Connect Provider (OP).
  

Problem conclusion

• The OIDC TAI is updated to add a configuration option for
  the
  OP's token revocation endpoint.  When logout is performed,
  if
  a revocation endpoint is configured, the revocation endpoint
  will be invoked for the refresh token.
  
  OPs should revoke the access token associated with the
  refresh
  token.  However, they are not required to do so.  An OIDC
  TAI
  configuration option is provided to instruct the TAI to
  perform a separate revocation request for the access token.
  This option defaults to FALSE.
  
  
  The following OIDC TAI properties are added:
  
  provider_<id>.revokeEndpointUrl
  default=(none)
  description=Specifies the endpoint URL for calling the
  OpenID
  Connect Provider's token revocation endpoint.
  
  provider_<id>.revokeAccessToken
  default=false
  description=By default, when a logout is performed, a
  revocation request is only made for the refresh token.  The
  OP should revoke both the refresh token and its
  associated access token with this request. When this
  property
  is set to true, a separate revocation request is made for
  the
  access token.
  
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.14 and 9.0.0.9.  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 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

• R850 PSY

     UP

• R900 PSY

     UP