PK85239: FIRST LOGIN WORKS, SECOND LOGIN FAILS UNTIL USER IS CLEARED FROM AUTH CACHE. SPECIFIC TO JAAS LOGIN, NEED PK27436 IN 6.1

Fixes are available

APAR status

Closed as program error.

Error description

Cookie is not set in jaas login when user is found within the
auth cache, then the ltpa token is not set and the SSO fails to
authorize user.

JAAS login module not working, the code doesn't set cookies
except on the first call (that is before the subject is cached).
Trace shows the following:

[6/1/06 13:03:00:157 EDT] 00000064 WebAuthentica >
  getCookieValue Entry
  WASReqURL

[6/1/06 13:03:00:157 EDT] 00000064 WebAuthentica <
  getCookieValue
  <null>

It found two cookies for some time it returned only one.

[6/1/06 13:02:59:045 EDT] 00000064 WebAttributes >
  createCookiesStatic Entry
[6/1/06 13:02:59:085 EDT] 00000064 WebAttributes <
  createCookiesStatic: returning 2 cookie(s) to add to response.
  Exit
[6/1/06 13:03:00:157 EDT] 00000064 WebAttributes >
  createCookiesStatic Entry
[6/1/06 13:03:00:157 EDT] 00000064 WebAttributes <
  createCookiesStatic: returning 1 cookie(s) to add to response.
  Exit

Local fix

none. Alternatively clear the auth cache between each login,
which is not a very good solution.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application Server
****************************************************************
* PROBLEM DESCRIPTION: Hashmap login via HTTP request fails    *
*                      if login information is cached in       *
*                      AuthCache.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In wsMapDefaultInboundLoginModue, if a cache key exists in
custom property and AuthCache returns a corresponding Subject
of the cache key value, it doesn't attach LTPAToken cookie,
because normally, a cookie is attached in commit phase, but in
this scenario, commit phase is skipped.

Problem conclusion

With this fix, LTPAToken is generated properly in this scenario.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.27 and 7.0.0.5.  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
PK85239
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-23
Closed date
2009-05-11
Last modified date
2009-05-11

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":"BU059","label":"IBM Software w\/o TPS"},"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:
29 December 2021

Tips

PK85239: FIRST LOGIN WORKS, SECOND LOGIN FAILS UNTIL USER IS CLEARED FROM AUTH CACHE. SPECIFIC TO JAAS LOGIN, NEED PK27436 IN 6.1

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?