PM69334: WS-SECURITY KERBEROS TOKEN GENERATOR ISN'T PICKING UP KERBEROS TOKEN FROM MICROSOFT WINDOWS NATIVE TICKET CACHE

Fixes are available

APAR status

Closed as program error.

Error description

When a Kerberos token exists in the Microsoft Windows native
ticket cache, Java security has access to the token, so the
WS-Security token generator should be able to pick it up and
generate it. However, WS-Security is unable to pick up the
token from the Microsoft Windows native ticket cache.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  WS-Security enabled JAX-WS applications     *
*                  and Kerberos                                *
****************************************************************
* PROBLEM DESCRIPTION: WS-Security Kerberos token generator    *
*                      does not pick up tokens from Microsoft  *
*                      Windows native ticket cache             *
****************************************************************
* RECOMMENDATION:  Apply a fix pack that contains this APAR.   *
****************************************************************
The WS-Security Kerberos token generator
KRBGenerateLoginModule is not picking up a Kerberos token that
is available in the Microsoft Windows native ticket cache.
When there is a token available in the Microsoft Windows native
ticket cache and a Kerberos token is not available through
other methods (username and password in callback handler or
Kerberos token on runAs subject), an error similar to the
following may occur:
[20/07/2012 16:52:20:241 EDT] 00000000 3
ecurity.wssapi.token.impl.KRBGenerateLoginModule
idForServiceTicket is null.
[20/07/2012 16:52:20:241 EDT] 00000000
ecurity.wssapi.token.impl.KRBGenerateLoginModule Error:
CWWSS7292E: Failed to login for Kerberos AP_REQ token
generation due to exception java.lang.NullPointerException
from Kerberos Token Profile processing runtime.
CWWSS7292E: Failed to login for Kerberos AP_REQ token
generation due to exception java.lang.NullPointerException
from Kerberos Token Profile processing runtime.

Problem conclusion

The WS-Security runtime dit not recognize that there is a
ticket in the Microsoft Windows native ticket cache.

The WS-Security runtime is updated to access a Kerberos token
in the Microsoft Windows native ticket cache.

The Kerberos token generator will use the following priority
when generating tokens:

1) Username and password specified on the callback handler
2) Ticket in runAs subject on the current thread
3) Ticket in Microsoft Windows native ticket cache

The ticket will only be used from the Microsoft Windows native
ticket cache if there is no username and password specified in
the token generator's callback handler, and there is no
Kerberos ticket on the current thread's runAs subject.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.27, 8.0.0.5, and 8.5.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
PM69334
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-07-20
Closed date
2012-07-24
Last modified date
2012-11-27

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

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

Document Information

Modified date:
29 October 2021

Tips

PM69334: WS-SECURITY KERBEROS TOKEN GENERATOR ISN'T PICKING UP KERBEROS TOKEN FROM MICROSOFT WINDOWS NATIVE TICKET CACHE

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

R850 PSY

Document Information

Share your feedback

Need support?