Fixes are available
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
APAR status
Closed as program error.
Error description
If the JAX-WS runtime in the Liberty profile sends a message with asymmetric digital signature and encryption to the JAX-WS runtime in the WebSphere Application Server full profile, a CWWSS6001E: Key object was not obtained. error may occur.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server users of * * WS-Security enabled JAX-WS applications * * with asymmetric digital signature and * * encryption * **************************************************************** * PROBLEM DESCRIPTION: CWWSS6001E error may occur when * * consuming a SOAP message that * * contains both asymmetric digital * * signature and encryption * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this * * APAR. * **************************************************************** When JAX-WS WS-Security is configured for both asymmetric digital signature and encryption of the Body element in the SOAP header, a "CWWSS6001E: Key object was not obtained." error may occur when consuming the message. A stack similar to the following will appear in an ffdc log: com.ibm.wsspi.wssecurity.core.SoapSecurityException: CWWSS6001E: Key object was not obtained. at com.ibm.wsspi.wssecurity.core.SoapSecurityException.format(SoapS ecurityException.java:57) at com.ibm.ws.wssecurity.keyinfo.KeyInfoConsumer.getKey(KeyInfoCons umer.java:202) at com.ibm.ws.wssecurity.dsig.SignatureConsumer.callKeyInfoConsumer (SignatureConsumer.java:1140) at com.ibm.ws.wssecurity.dsig.SignatureConsumer.callKeyInfoConsumer (SignatureConsumer.java:1104) at com.ibm.ws.wssecurity.enc.EncryptionConsumer.decrypt(EncryptionC onsumer.java:687) ... This issue will not occur when the both the sender and receiver of the message are the WS-Security runtime in the WebSphere Application Server full profile. It is most likely to happen when the Apache CXF runtime is the sender of the message. The Liberty profile in WebSphere Application Server 8.5.5 uses the Apache CXF runtime.
Problem conclusion
The JAX-WS WS-Security runtime in the WebSphere Application Server full profile expects a KeyInfo element in the EncryptedData element in the Body only when a message with symmetric digital signature and encryption is being processed. If a KeyInfo element appears in this location when a message with asymmetric digital signature and encrypiton is being processed, assumptions are made by the runtime that are not true and you can get unexpected results. The JAX-WS WS-Security runtime in the WebSphere Application Server full profile is updated to exit the symmetric digital signature and encryption path if asymmetric digital signature and encryption are configured. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.31, 8.0.0.7, and 8.5.5.1. 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
PM88011
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-04-29
Closed date
2013-05-16
Last modified date
2013-05-16
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
R850 PSY
UP
Document Information
Modified date:
12 January 2022