PM07098: USER SUBJECT REMAINS IN AUTH CACHE AFTER LOGOUT, CAUSES JAVA.UTIL.NOSUCHELEMENTEXCEPTION ON SUBSEQUENT LOGIN ATTEMPTS

Fixes are available

APAR status

Closed as program error.

Error description

When a user performs a logout, the subject for that user
remains in the auth cache. A subsequent login will find the
subject from the cache and the subject will not contain public
credentials, thus producing a java.util.NoSuchElementException.

The expected behavior would be that during a user logout
the subject for that user is removed from the auth cache. If the
custom logout is not doing this, then it is suggested that it
does. The APAR is needed to protect from when the subject is
left in the auth cache. In that case, the login must continue as
if the subject was not found in the cache.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0                        *
****************************************************************
* PROBLEM DESCRIPTION: For WebSphere Application Server, a     *
*                      user login fails with                   *
*                      java.util.NoSuchElementException.       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
For WebSphere Application Server, the login of a given user
fails with java.util.NoSuchElementException.
The stack trace is as follows,

[10/02/01 16:40:02:364 JST] 00000088 ContextManage 3   login
failed: java.util.NoSuchElementException
 at
java.util.HashMap$HashIterator.nextEntry(HashMap.java:1094)
 at java.util.HashMap$KeyIterator.next(HashMap.java:1128)
 at
com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManag
erImpl.java:3152)

Problem conclusion

The security code was modified to validate that a subject
retrieved from the authentication cache has the corresponding
public credentials.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.33 and 7.0.0.11.  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
PM07098
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-09
Closed date
2010-03-26
Last modified date
2010-03-26

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM07098: USER SUBJECT REMAINS IN AUTH CACHE AFTER LOGOUT, CAUSES JAVA.UTIL.NOSUCHELEMENTEXCEPTION ON SUBSEQUENT LOGIN ATTEMPTS

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?