PI55697: OPENID CONNECT RELYING PARTY: NO ENTRY IN CACHE FOR STATEID

Fixes are available

APAR status

Closed as program error.

Error description

OpenID Connect Relying Party: No entry in cache for stateid
happens in a cluster environment.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Administrators of IBM WebSphere Application *
*                  Server and OpenID Connect                   *
****************************************************************
* PROBLEM DESCRIPTION: CWTAI2007E OpenID Connect error may     *
*                      occur in a cluster environment          *
****************************************************************
* RECOMMENDATION:  Install a fix pack that contains this       *
*                  APAR.                                       *
****************************************************************
When a resource is protected by the OpenID Connect Relying
Party TAI in a cluster environment, an error like the
following may occur during login:
[1/4/16 14:05:21:107 CET] 00000057 WebAuthentica E
SECJ0126E: Trust Association failed during validation. The
exception is
com.ibm.websphere.security.WebTrustAssociationFailedException:
CWTAI2007E: TheOpenID Connect replying party (RP) encountered
a failure during the login. The exception is [No entry in
cache for stateid:  [6r0sco232ft5cstviumgm6i8fe]. Check the
logs for details that lead to this exception.

Problem conclusion

When a request is made to a resource producted by the OpenID
Connect Relying Party TAI, a login is initiated to the OpenID
Connect Provider (OP). After login, the OP sends a response
back to the TAI.  Before login, the TAI saves state
information about the login request in a cache using the
6r0sco232ft5cstviumgm6i8fe as the key.  When the
response is received from the OP, the TAI retrieves the
request information from the cache.  In a cluster environment,
when the OP responds, the individual cluster member that
receives the response is indeterminate.  If the cluster member
that retrieved the response is not the member that cached the
login request, the CWTAI2007E error will occur.

This issue can normally be resolved by using session affinity.
However, if you are using some front-end application to load
balance the cluster member resources, using session affinity
won't work.

The OpenID Connect TAI is updated in the following ways:

1) The dynacache put is set to PUSH
2) The session data that is stored in the cache is added to
the request sent to the OP so that any cluster member that
receives the response from the OP has access to it.  This
means that if a server that receives the response cannot find
the key in the cache, it can find the information it needs
from the response.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.0.0.13 and 8.5.5.10.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Keywords: IBMWL3WSS, OIDC

Temporary fix

Comments

APAR Information

APAR number
PI55697
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-01-19
Closed date
2016-04-08
Last modified date
2016-04-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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI55697: OPENID CONNECT RELYING PARTY: NO ENTRY IN CACHE FOR STATEID

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?