Fixes are available
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
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.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
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.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 the SAML Web SSO TAI ACSTrustAssociationInterceptor uses the Cell Level default trust store for signer certificates, after the server is started, any signer certificate added to the trust store are not picked up immediately. If a valid SAML response is sent that was signed by the certificate that was just added, the request is rejected. When the server is restarted, the request will be successful.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server * * administrators of WS-Security enabled * * JAX-WS applications and SAML Web SSO TAI * **************************************************************** * PROBLEM DESCRIPTION: WS-Security and SAML Web SSO do not * * recognize updates to centralized * * keystores * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this * * APAR. * **************************************************************** When an application is configured to use a centralized keystore for its trust store, when certificates are added or deleted from the keystore, the updates are not recognized by the application. For instance, a WS-Security enabled JAX-WS application is configured with a centralized keystore in its X.509 callback handler for digital signature. If a certificate is added to the keystore, a message that is signed with that certificate will be rejected because it is not trusted. Another example: The ACSTrustAssociationInterceptor is configured with a centralized keystore for its trust store. If a certificate is deleted from the keystore, a message that is signed with that certificate will not be rejected, but it should be. When the application server is restarted, updates to the centralized keystore are recognized by the applications and the trust evaluation behaves as expected. This APAR does not apply to hardcoded keystores. Updates to hardcoded keystores are not intended to be recognized until the application server is restarted.
Problem conclusion
When a centralized keystore is opened by the runtime, an instance of the object is cached. When the keystore is modified, the WebSphere runtime creates a new object instead of updating the original object, so the object that was cached has become obsolete. The runtime is updated to not cache the keystore objects for centralized keystores. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.27, 8.0.0.5, and 8.5.0.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Keywords: IBMWL3WSS, SAMLWSSO
Temporary fix
Comments
APAR Information
APAR number
PM69064
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-07-17
Closed date
2012-07-24
Last modified date
2015-10-29
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
R850 PSY
UP
Document Information
Modified date:
29 October 2021