PK92003: Using custom tokens with JAX-WS WS-Security fails with the message CWWSS5371E

Fixes are available

APAR status

Closed as program error.

Error description

Custom tokens don't currently work with JAX-WS WS-Security.

When trying to generate or consume a custom Security token from
JAX-WS there are several SoapSecurityException errors that
occur.  For example:

Exception = com.ibm.wsspi.wssecurity.core.SoapSecurityException
Source =
com.ibm.ws.wssecurity.handler.WSSecurityConsumerHandler.invoke
probeid = %C
Stack Dump =
com.ibm.wsspi.wssecurity.core.SoapSecurityException:
CWWSS5371E: The token consumer/generator configuration has a
null class instance. The current token consumer/generator
configuration string representation is
com.ibm.ws.wssecurity.confimpl.PrivateConsumerConfig$TokenConsum
erConfIm
pl(className=[us.ibm.security.IBMConsumer],
type=[{http://www.cm.es}TokenCas],
jaasConfig=[application.ibm.IBMToken],
jaasConfigProperties=[{}],
callbackHandler=[com.ibm.ws.wssecurity.confimpl.PrivateCommonCon
fig$Call
backHandlerConfImpl(className=[us.ibm.security.IBMHandler],
keyStore=[null], keyInformation=[null],
trustAnyCertificate=[false],
provider=[null], pkixBuilderParams=[null], userId=[null],
userPassword=[XXXXXXXX], properties=[{}])],
usedForVerification=[false],
usedForDecryption=[false],
properties=[{com.ibm.wsspi.wssecurity.core.NonceClockSkew=0,
com.ibm.wsspi.wssecurity.core.NonceMaxAge=300000}]).
at com.ibm.wsspi.wssecurity.core.SoapSecurityException.format
(SoapSecurityException.java:77)
at com.ibm.ws.wssecurity.confimpl.PrivateConsumerConfig$
TokenConsumerConfImpl.validate(PrivateConsumerConfig.java:1384)
at com.ibm.ws.wssecurity.confimpl.PrivateConsumerConfig.
validate(PrivateConsumerConfig.java:876)
at com.ibm.ws.wssecurity.handler.PolicyInboundConfig.init
(PolicyInboundConfig.java:2556)
at com.ibm.ws.wssecurity.handler.PolicyInboundConfig.<init>
(PolicyInboundConfig.java:223)
at com.ibm.ws.wssecurity.handler.WSSecurityBindingLoaderImpl.
loadCustom(WSSecurityBindingLoaderImpl.java:369)

Local fix

Current work around is: If a customer would like to generate
an LTPA token based on the HTTP cookie, user can still create a
custom token generator that the ws-security runtime can use to
emit the LTPA token.
A custom token generator would be used to emit the token on the
client-side, and use the built-in LTPA token consumer to consume
the token on the server-side.

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server Web Services   *
*                  users of WS-Security enabled JAX-WS         *
*                  applications that want to use custom tokens *
****************************************************************
* PROBLEM DESCRIPTION: If WS-Security for a JAX-WS             *
*                      application is configured to use a      *
*                      custom token, the token won't be        *
*                      emitted                                 *
****************************************************************
* RECOMMENDATION:  Apply a fix pack that contains this APAR.   *
****************************************************************
If WS-Security for a JAX-WS application is configured to use a
custom token for any operation, the token won't be emitted or
consumed.  If a custom token generator or consumer is invoked,
a java.lang.NoClassDefFoundError error similar to the following
will occur:

Exception: javax.xml.ws.WebServiceException:
java.security.PrivilegedActionException:
com.ibm.wsspi.wssecurity.core.SoapSecurityException:
security.wssecurity.WSSContextImpl.s02:
com.ibm.websphere.security.WSSecurityException: Exception
org.apache.axis2.AxisFault: CWWSS6521E: The Login failed
because of an exception:
javax.security.auth.login.LoginException:
java.lang.NoClassDefFoundError:
com.ibm.wsspi.wssecurity.wssapi.OMStructure at
java.lang.ClassLoader.defineClassImpl(Native Method) at
...

Problem conclusion

The WS-Security code for JAX-WS applications was updated to
allow custom tokens to be emitted or consumed as configured.

Custom token generators and consumers that were built for use
with WS-Security for JAX-RPC applications cannot be used with
WS-Security for JAX-WS applications.

This same problem is fixed in WebSphere Application Server
Feature Pack for Web Services by PK80478.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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
PK92003
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
2009-07-22
Closed date
2009-10-09
Last modified date
2009-10-09

APAR is sysrouted FROM one or more of the following:

PK80478
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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
24 October 2021

Tips

PK92003: Using custom tokens with JAX-WS WS-Security fails with the message CWWSS5371E

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

Document Information

Share your feedback

Need support?