PM45259: NULLPOINTEREXCEPTION WHEN WS-SECURITY ATTEMPTS TO GENERATE AN LTPA TOKEN FROM RUNAS SUBJECT

Fixes are available

APAR status

Closed as program error.

Error description

If WS-Security is configured to generate LTPA Tokens from the
current WebSphere identity, but no user has been authenticated,
a java.lang.NullPointerException may occur.

Local fix

```
na
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server            *
*                  users of WS-Security enabled Web Services   *
*                  and LTPA tokens                             *
****************************************************************
* PROBLEM DESCRIPTION: If WS-Security generates LTPA Tokens    *
*                      from the current WebSphere identity, a  *
*                      java.lang.NullPointerException may      *
*                      occur.                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If WS-Security is configured to generate an LTPA Token from the
current WebSphere identity, but no user has been authenticated,
a java.lang.NullPointerException error may occur.
The following may be observed in the SystemOut.log:
faultString: com.ibm.wsspi.wssecurity.SoapSecurityException:
WSEC6526E:Unable to handle the callbacks by the callback
handler
[com.ibm.wsspi.wssecurity.auth.callback.LTPATokenCallbackHandler
]:java.io.IOException: Error doing token propagation
processing:
java.lang.NullPointerException: null
The WS-Security runtime will attempt to use the current
WebSphere identity when there is no userid and password
associated with the LTPA Token Generator callback handler.

Problem conclusion

The WS-Security runtime assumed that, if a non-null runAs
Subject was returned from base security, a non-null
AuthenticationToken would always be present on that Subject.
That assumption is not valid.

Since the LTPA token is generated from the AuthenticationToken
on the runAs subject, when the AuthenticationToken is null, an
LTPA token cannot be generated for that runAs subject.

The WS-Security runtime is updated to ensure that there is an
AuthenticationToken present on the runAs subject before
attempting to create an LTPA token from the current WebSphere
identity.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.0.43, 7.0.0.23 and 8.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
PM45259
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-08-08
Closed date
2011-11-21
Last modified date
2011-11-28

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
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

PM45259: NULLPOINTEREXCEPTION WHEN WS-SECURITY ATTEMPTS TO GENERATE AN LTPA TOKEN FROM RUNAS SUBJECT

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

R800 PSY

Document Information

Share your feedback

Need support?