Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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.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
JAX-WS WS-security runtime does not accept SecurityTokenReference elements in the SOAP Security header that refer to non-SAML supporting tokens.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 users * * of WS-Security enabled JAX-WS applications * * * **************************************************************** * PROBLEM DESCRIPTION: JAX-WS WS-security runtime does not * * accept SecurityTokenReference * * elements that refer to non-SAML * * supporting tokens. * **************************************************************** * RECOMMENDATION: Install a fix pack that includes this APAR. * **************************************************************** JAX-WS WS-security runtime does not accept SecurityTokenReference elements in the SOAP Security header that refer to non-SAML supporting tokens. In order to sign a security token using STR Dereference Transform (STR-Transform), a SecurityTokenReference with a reference to the security token must exist in the message. Following is an example of a SOAP Security header with a SecurityTokenReference to a BinarySecurityToken: <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401- wss-wssecurity-secext-1.0.xsd"> <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-w ss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-20040 1-wss-soap-message-security-1.0#Base64Binary" ID="binarySecurityToken1" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-w ss-x509-token-profile-1.0#X509v3" wsu:Id="binarySecurityToken1"> (...base64EncodedData...) </wsse:BinarySecurityToken> <wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-w ss-wssecurity-utility-1.0.xsd" wsu:Id="strrefId1"> <wsse:Reference URI="#binarySecurityToken1"></wsse:Reference> </wsse:SecurityTokenReference> .... </wsse:Security> When the error occurs, entries similar to the following may be observed in the trace file: [02.12.10 15:56:27:483 CET] 0000001a X509ConsumeLo E CWWSS5520E: An exception occurred during token processing. The exception is: java.security.cert.CertificateException: Unable to initialize, java.io.IOException: DerInputStream.getLength(): lengthTag=127, too big. at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:270) at com.ibm.crypto.provider.X509Factory.engineGenerateCertificate(Un known Source) at java.security.cert.CertificateFactory.generateCertificate(Certif icateFactory.java:409) at com.ibm.ws.wssecurity.util.CertificateUtil.generateCertificate(C ertificateUtil.java:433) at com.ibm.ws.wssecurity.util.CertificateUtil.generateX509Certifica te(CertificateUtil.java:406) at com.ibm.ws.wssecurity.wssapi.token.impl.X509ConsumeLoginModule.p rocessElement(X509ConsumeLoginModule.java:1026) ...
Problem conclusion
The JAX-WS WS-Security runtime is recognizing the correct type of the token. However, it is passing the SecurityTokenReference element itself into the token consumer instead of the referenced token. With the exception of the SAML token consumer, the token consumers only understand their own token element and element format (UsernameToken or BinarySecurityToken for exampe); they do not understand, nor can process a SecurityTokenReference. The runtime should recognize that the inbound SecurityTokenReference refers to a token that has already been consumed then continue to the next element in the message. The JAX-WS WS-Security runtime is updated to properly process SecurityTokenReference elements that refer to non-SAML supporting tokens. The fix for this APAR is currently targeted for inclusion in 7.0.0.19 pack. 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
PM28883
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
2010-12-14
Closed date
2011-05-13
Last modified date
2011-05-13
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
Document Information
Modified date:
27 October 2021