Fixes are available
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
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
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
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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
WebSphere Application Server centralized key stores cannot be used for the generation or consumption of SAML tokens using JAX-WS WS-Security.
Local fix
NA
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 users * * of WS-Security enabled JAX-WS web services * * applications, SAML tokens, and centralized * * key stores * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server * * centralized key stores cannot be used * * to process SAML tokens with JAX-WS * * WS-Security * **************************************************************** * RECOMMENDATION: Install a fix pack that includes this APAR. * **************************************************************** If the JAX-WS WS-Security runtime is configured using WebSphere Application Server centralized key stores for the generation or consumption of SAML tokens, the SAML token may not be processed. A message like the following can be seen in a trace.log: [2/9/10 18:41:33:798 EST] 0000001b WSSecurityGen E CWWSS5514E: An exception while processing WS-Security message. [2/9/10 18:41:33:818 EST] 0000001b WSSecurityGen 3 Error in security handler: org.apache.axis2.AxisFault: CWWSS6521E: The Login failed because of an exception: javax.security.auth.login.LoginException: com.ibm.websphere.wssecurity.wssapi.WSSException Information that is logged into an FFDC file will vary depending on the location where the key store was configured. The following is one is example: javax.security.auth.login.LoginException: com.ibm.websphere.wssecurity.wssapi.WSSException at com.ibm.ws.wssecurity.wssapi.token.impl.SAMLGenerateLoginModule. selfIssueSAMLToken(SAMLGenerateLoginModule.java:517) at com.ibm.ws.wssecurity.wssapi.token.impl.SAMLGenerateLoginModule. processClientSideSAMLIssue(SAMLGenerateLoginModule.java:297) at com.ibm.ws.wssecurity.wssapi.token.impl.SAMLGenerateLoginModule. processClientSideSAML(SAMLGenerateLoginModule.java:248) at com.ibm.ws.wssecurity.wssapi.token.impl.SAMLGenerateLoginModule. createSAMLToken(SAMLGenerateLoginModule.java:232) at com.ibm.ws.wssecurity.wssapi.token.impl.SAMLGenerateLoginModule. login(SAMLGenerateLoginModule.java:184)
Problem conclusion
The runtime always requires a password be supplied with a key store in the WS-Security policy bindings. If a password is not supplied, an error will occur. Because WebSphere centralized key stores must be configured in the bindings without passwords, an error will always occur when a centralized key store is configured. The runtime is updated to not require a password when a WebSphere centralized key store is configured. The runtime is also updated to emit key store errors immediately when they occur so that the reason for the failure doesn't get obscured. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.15. 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
PM13063
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-04-25
Closed date
2010-09-07
Last modified date
2010-09-07
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:
24 October 2021