PM53387: CWWSS5620E: WEB SERVICE SECURITY SIGNING FAILS WITH TWO CERTIFICATES ARE ASSOCIATED TO AN X.509 TOKEN CONSUMER.

Fixes are available

APAR status

Closed as program error.

Error description

In WS-Security policy bindings, when more than one signing key
information object associated with an X.509 token consumer is
assigned to a single inbound signed message part, a 'Signature
verification failed' error may occur.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  WS-Security enabled JAX-WS applications     *
****************************************************************
* PROBLEM DESCRIPTION: When more than one X.509 token          *
*                      consumer is assigned to a single        *
*                      signed message part, a CWWSS5620E       *
*                      error may occur.                        *
****************************************************************
* RECOMMENDATION:  Install a fix pack that includes this       *
*                  APAR.                                       *
****************************************************************
In WS-Security policy bindings, when more than one signing key
information object that is associated with an X.509 token
consumer is assigned to a single inbound signed message part,
a message similar to the following may occur:
CWWSS5620E: Signature verification failed: Core validity=false
Signed info validity=false Signed info message='SignatureValue
mismatched.' Ref[0](validity=true message='Ok.'
uri='#wssecurity_signature_id_20' type='null').
This error will most likely occur when the X.509 token is not
sent in the message.  For instance when KEYID or
X.509IssuerSerial are being used.

Problem conclusion

The WS-Security runtime caches X.509 certificates.  For X.509
tokens that are not in the message, the key in the cache is
the KEYID or X509IssuerSerial string.  When one X.509 token
consumer gets a cache hit, it then 'assumes' that the
certificate found belongs to that consumer.  If the consumer
is for a BinarySecurityToken that is in the message, that is
ok.  However, if the consumer is for a certificate that has
been configured on the callback handler, the token consumer
may detect a cache hit for KEY1, when its callback handler is
configured for KEY2.  When this happens, although KEY1 was
passed in the message, KEY2 will be used to verify the
signature.

The X.509 token consumer in the WS-Security runtime is updated
to ensure that a certificate retrieved from the cache is the
one that it has configured before the certificate is used.  If
the certificates do not match, processing will continue as if
no certificate were retrieved from the cache.

The fix for this APAR is currently targeted for inclusion in
fix packs 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
PM53387
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
2011-12-01
Closed date
2012-01-26
Last modified date
2012-05-25

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

[{"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:
28 October 2021

Tips

PM53387: CWWSS5620E: WEB SERVICE SECURITY SIGNING FAILS WITH TWO CERTIFICATES ARE ASSOCIATED TO AN X.509 TOKEN CONSUMER.

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?