Fixes are available
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
PM12971; 6.1.0.35: jax-rpc ws-security str-transform processing is incorrect
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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
APAR status
Closed as program error.
Error description
When a SAML token is sent in the WS-Security header of a SOAP message, the WS-Security runtime will always encounter the following error, regardless of the mustUnderstand setting: faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.securityExcept ion faultString: com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5503E: Unknown element wsse:SecurityTokenReference in the wsse:Security element. faultActor: null faultDetail: com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5503E: Unknown element wsse:SecurityTokenReference in the wsse:Security element. at com.ibm.ws.webservices.engine.WebServicesFault. makeUserFault(WebServicesFault.java:223) at com.ibm.ws.webservices.wssecurity.handler. WSSecurityConsumerBase.invoke(WSSecurityConsumerBase.java:101) . The wsse:Security header with a SAML token looks as follows. <wsse:Security> <wsse:SecurityTokenReference soapenv:mustUnderstand="1" wsu:Id=" SecurityTokenReference-3720982240"> <wsse:Embedded> <saml:Assertion> ... </saml:Assertion> </wsse:Embedded> </wsse:SecurityTokenReference> </wsse:Security> NOTE: This is a problem that did not exist prior to WebSphere Application Server 6.0.2.29.
Local fix
Taking the SAML token out of the SecurityTokenReference and putting it straight under the wss:security header works example <wsse:Security> <saml:Assertion> ... </saml:Assertion> </wsse:Security>
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users of * * WS-Security enabled web services * * applications that receive SAML tokens * **************************************************************** * PROBLEM DESCRIPTION: The WS-Security runtime does not skip * * an unrecognized SAML token when * * mustUnderstand='0' in the SOAP * * Security header * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this APAR. * **************************************************************** When a SAML token is sent in the WS-Security header of a SOAP message, the WS-Security runtime will ordinarily throw an exception unless a custom handler is configured for the SAML token. If mustUnderstand='0' in the WS-Security header, the SAML token should be skipped by the WS-Security runtime, but an exception still occurs. A message similar to the following can be found in the trace or an FFDC log: faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.securityExcept ion faultString: com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5503E: Unknown element wsse:SecurityTokenReference in the wsse:Security element. faultActor: null faultDetail: com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5503E: Unknown element wsse:SecurityTokenReference in the wsse:Security element. at com.ibm.ws.webservices.engine.WebServicesFault. makeUserFault(WebServicesFault.java:223) at com.ibm.ws.webservices.wssecurity.handler. WSSecurityConsumerBase.invoke(WSSecurityConsumerBase.java:101) ...
Problem conclusion
The root of the problem is that, when an element occurs in the wsse namespace, and the element is not explicitly BinarySecurityToken or UsernameToken, an error will occur regardless of the mustUnderstand setting. Because the SAML token is a SecurityTokenReference in the wsse namespace, an error will occur regardless of the mustUnderstand setting. The WS-Security runtime was updated to honor the mustUnderstand setting when tokens are encountered in the wsse namespace that are not a BinarySecurityToken or a UsernameToken. This, in effect, will enable the WS-Security runtime to skip an unrecognized SAML token when the mustUnderstand setting for the SOAP Security header is '0'. The wsse namespace is: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri ty-secext-1.0.xsd The fix for this APAR is currently targeted for inclusion in fix packs 6.0.2.39, 6.1.0.29, 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
PK85910
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-05
Closed date
2009-07-11
Last modified date
2009-09-24
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
R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
Document Information
Modified date:
29 December 2021