Fixes are available
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
SAML tokens cached by WS-Security can only be used by client applications that also use a BindingProvider. If a client application does not use a BindingProvider, SAML tokens will not be cached. This has profound negative effects on performance.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server users of * * WS-Security enabled JAX-WS applications * * and SAML * **************************************************************** * PROBLEM DESCRIPTION: JAX-WS WS-Security will only cache * * SAML tokens for applications that * * have a BindingProvider available. * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this * * APAR. * **************************************************************** Depending on the availability of the BindingProvider, the WS-Security SAMLGenerateLoginModule may not cache SAML tokens. Also, even if the desired SAML tokens had been cached, SAMLGenerateLoginModule may not be able to use the SAML token that exists in the cache. This can have negative performance implications since more requests to the STS will be made than are necessary.
Problem conclusion
When SAMLGenerateLoginModule caches a SAML token, the BindingProvider is used as a cache key. Because of this, caching is only available to applications that have access to the BindingProvider. The WS-Security runtime is updated so that the cache no longer has a dependency on the BindingProvider. The size and timeout of the cache are controlled with JVM System properties, so they are fixed at application server or client JVM startup. The new implementation allows the WS-Security code to share a cache of SAML tokens. The following properties are added: com.ibm.wsspi.wssecurity.saml.client.SamlTokenCacheTimeout com.ibm.wsspi.wssecurity.saml.client.SamlTokenCacheEntries com.ibm.wsspi.wssecurity.saml.signature.SignatureCacheTimeout com.ibm.wsspi.wssecurity.saml.signature.SignatureCacheEntries com.ibm.wsspi.wssecurity.saml.client.SamlTokenCacheTimeout Time in minutes, the length of time a SAML token could be maintained in a client cache. Defaults to 60 minutes. com.ibm.wsspi.wssecurity.saml.client.SamlTokenCacheEntries The maximum number of cache entries that can be maintained. Defaults to 250. com.ibm.wsspi.wssecurity.saml.signature.SignatureCacheTimeout Time in minutes a SAML token is to be cached. A signature validation does not need to be repeated while the SAML token is cached. Defaults to 60 minutes. com.ibm.wsspi.wssecurity.saml.signature.SignatureCacheEntries The maximum number of signature cache entries that can be maintained for a SAML consumer token. Defaults to 1000. Note that only SAMLGenerateLoginModule will cache SAML tokens in outbound request messages for client applications. SAMLConsumeLoginModule will not cache SAML tokens that exist in inbound response messages for client applications. A SAML token that was sent in an outbound request using SAMLGenerateLoginModule will be placed in the cache after a successful response has been received from the provider application. If an error is received, the token will not be cached. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.27. 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
PM30921
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-01-20
Closed date
2012-10-01
Last modified date
2012-10-01
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
Document Information
Modified date:
27 October 2021