PM44052: LOGIN WITH LTPATOKEN MIGHT FAIL DUE TO GSSENCODEDECODEEXCEPTION

Fixes are available

APAR status

Closed as program error.

Error description

Occasionally, login attempts via WebServices failed due to lack
of LTPAToken, even valid LTPAToken is supplied. When this
condition happens, followin sequence of events are logged in a
trace file:

[7/15/11 12:19:12:202 CEST] 00000055 ltpaLoginModu >  login()
Entry
[7/15/11 12:19:12:202 CEST] 00000055 ContextManage >
getDefaultRealm Entry
[7/15/11 12:19:12:202 CEST] 00000055 ContextManage <
getDefaultRealm Exit
                                 DefailutRealm:389
[7/15/11 12:19:12:205 CEST] 00000055 wsMapDefaultI >
wsMapDefaultInboundLoginModule() Entry

As you can see, there is no trace entry which indicates that
login() method in lptaLoginModule is exiting.

Local fix

```
NA
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Occasionally, login attempts via        *
*                      WebServices failed, even when a valid   *
*                      LTPAToken is supplied                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When login method in LTPALoginModule is processed, a
method which detects whether a incoming token is a GSSToken
or not, occasionally throws an exception even there is a valid
token.
As a result, this exception triggers LPTALoginModule aborting
from login process.

Problem conclusion

With this fix, the method in question was modified not to
throw exceptions.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.21 and 8.0.0.2.  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
PM44052
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-19
Closed date
2011-08-09
Last modified date
2011-08-09

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP
R800 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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM44052: LOGIN WITH LTPATOKEN MIGHT FAIL DUE TO GSSENCODEDECODEEXCEPTION

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

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?