Fixes are available
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.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
The clockSkew property is not properly changing the Conditions bounds in a SAML assertion. ********************************** Client system time: 8/12/2011 2:18 PM server system time: 8/13/2011 2:18 PM clockSkew defined in server.bindings.xml 1440 min <Conditions NotBefore="2011-08-12T14:15:48Z" NotOnOrAfter="2011-08-13T02:15:48Z"> Results in the same error message: CWWSS6521E: The Login failed because of an exception: javax.security.auth.login.LoginException: CWSML2039E: InvalidSAML assertion. ..... Conclusion: The clockSkew property is not properly changing the Conditions bounds. ***********************************************
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 * * and V8.0 users of WS-Security enabled * * JAX-WS applications and SAML * **************************************************************** * PROBLEM DESCRIPTION: Application Server will throw an * * exception if a SAML assertion does * * not contain a notOnOrAfter attribute * * and clockSkew is not used. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere Application Server V7.0 will throw an exception if a SAML assertion does not contain a notOnOrAfter attribute. Additionally the clockSkew property is not applied to the assertion on WebSphere Application Server V7.0 or V8.0.
Problem conclusion
The code checked for the presence of the notOnOrAfter attribute and in V8.0 was not properly loading the clockSkew property. Web Services configured with SAML 1.1 or SAML 2.0 that processed SAML assertions that do not contain the notOnOrAfter attribute, or where application of the clockSkew property was required would fail with the "CWWSS6521E: The Login failed because of an exception: javax.security.auth.login.LoginException: CWSML2039E: Invalid SAML assertion." message. Code has been changed in V7.0 not to throw an exception if the SAML assertion does not contain the notOnOrAfter attribute. In addition, on both V7.0 and V8.0 the code that loads the clockSkew property has been corrected to properly load that property. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.23 and 8.0.0.3. 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
PM45775
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-08-16
Closed date
2011-11-21
Last modified date
2011-11-21
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:
27 October 2021