Fixes are available
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.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
A web application and a web service application are installed on an application server (server A). An EJB application is installed on another server (server B). The web application invokes the web service which calls the remote EJB. The web application and the EJB application are protected by roled based security. The web application uses SAML Web SSO as authentication mechanism, and ID assertion is enabled. The SAML token Identify provider is a TFIM server. To make this scenario working, the SAML issuer name should be added as the WAS trusted realm for both server A and server B. The issuer name string is: https://test.server.ibm.com:9449/test/saml2fed/saml20 When running this scenario, got test failure and the following exception appears in the server1 FFDC: [10/12/11 21:43:44:096 CDT] FFDC Exception:com.ibm.websphere.security.WSSecurityException SourceId:readObject ProbeId:1112 Reporter:com.ibm.ws.security.context.ContextImpl@7f647f64 com.ibm.websphere.security.WSSecurityException: the realms do not match at com.ibm.ws.security.context.ContextImpl.doLogin(ContextImpl.java :781) at com.ibm.ws.security.context.ContextImpl.deserializeSubjects(Cont extImpl.java:1144) at com.ibm.ws.security.context.ContextImpl.readObject(ContextImpl.j ava:1110) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.jav a:1044) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java: 1866) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.j ava:1770) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:134 6) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:365) at com.ibm.ws.websvcs.utils.SecurityContextMigrator$6.run(SecurityC ontextMigrator.java:361) at java.security.AccessController.doPrivileged(AccessController.jav a:251) at com.ibm.ws.websvcs.utils.SecurityContextMigrator.migrateThreadTo Context(SecurityContextMigrator.java:358)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: If there is more than one slash * * character in the access ID, * * the security code may not extract * **************************************************************** * RECOMMENDATION: * **************************************************************** Slash character is used as a demimitor of realm name and unique user id in the security code. So, the original assumption was that there was only one slash character in Access ID string. However, there are some situations that there are multiple slashes existing in realm name. To support this situation, the code needs to be implemented with more sophisticated way to find out the realm name in Acces ID.
Problem conclusion
With this fix, if there are multiple slash characters in Access ID, the realm name is extracted based on number of slashes in the string. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.21 and 8.0.0.2. 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
PM51523
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-03
Closed date
2011-11-10
Last modified date
2011-11-10
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
Document Information
Modified date:
28 October 2021