PK75058: A SUBJECT WHICH WAS CONSTRUCTED VIA TAI DOES NOT GET CACHED CORRECTLY.

Fixes are available

APAR status

Closed as program error.

Error description

The case of user ID which is returned by Trust Association
Interceptor (TAI) does not match the case of user ID in user
registry. the security code doesn't construct a cache entry
which has user ID as same case as what TAI returns.
As a result, each request from the same user is revalidated
by the security code against user registry.  The end user
sees slow response time.
-
This is the scenario:
1) User "a0aaa" attempts to invoke url
"https://intranet.hostanme.com/xxxxxx" or
"https://intranet.hostname.com/xxxxxxxx/*".
2) TAM does not know user, reads TAM ldap, gets user groups, and
confirms group access to url.
3) TAM knows user, adds "iv-user=a0aaa" to request header and
forwards request to app server.
4) WebSphere reads "iv-user=a0aaa", does not know user, asks
eDirectory who is user "cn=a0aaa".
5) eDirectory search succeeds.  LDAP searches are case
insensitive.  eDirectory says, "cn=a0aaa" is "cn=A0AAA".
6) WebSphere asks eDirectory for "cn=A0AAA" groups and confirms
group access to url.
7) WebSphere returns page.
8) End user parses page and issues request for imbedded images,
etc.
9) Repeat steps 3 - 8.

Local fix

None
 -
Search Keywords:
user registry slow loop performance security hang

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
****************************************************************
* PROBLEM DESCRIPTION: Authentication Cache does not have a    *
*                      cache key which corresponds a user ID   *
*                      from TAI.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When TAI returns a user ID as a result of TAI authentication,
the security code doesn't use this user ID as one of cache key
for Authentication Cache.
As a result, if the case of user ID from TAI and ones of user
ID in user registry are not identical, subsequent
authentication requests will not reuse the cache entry but
will access the user registry again.

Problem conclusion

With this fix, the security code uses a user ID from TAI as
one of cache key of Authentication Cache.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.23 and 7.0.0.3.  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
PK75058
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
2008-11-05
Closed date
2008-12-10
Last modified date
2008-12-10

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

PK75058: A SUBJECT WHICH WAS CONSTRUCTED VIA TAI DOES NOT GET CACHED CORRECTLY.

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?