Fixes are available
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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
Description: When using setOneTimeUse(true) duplicate OneTimeUse (for SAML 2.0) and DoNotCacheCondition (for SAML 1.1) entries are being set. Here's one example. <saml2:Conditions NotBefore="2010-11-09T15:49:22.68Z" NotOnOrAfter="2010-11-09T15:54:22.68Z"> <saml2:OneTimeUse> <saml2:OneTimeUse/> </saml2:OneTimeUse> </saml2:Conditions> Fix the code creating duplicate entries.
Local fix
<NONE>
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 users * * of WS-Security enabled JAX-WS applications * * and SAML * **************************************************************** * PROBLEM DESCRIPTION: Duplicate OneTimeUse and * * DoNotCacheCondition assertions are * * being created in a SAML Token. * **************************************************************** * RECOMMENDATION: Install a fix pack that includes this APAR * **************************************************************** For SAML 2.0, a user may attempt to set OneTimeUse using the SAML API. One example would be: RequesterConfig reqData=samlFactory.newBearerTokenGenerateConfig(); reqData.setOneTimeUse(true); When the SAML token is created, the resulting condition will contain duplicate OneTimeUse assertions, such as this one: <saml2:Conditions NotBefore="2010-11-09T15:49:22.68Z" NotOnOrAfter="2010-11-09T15:54:22.68Z"> <saml2:OneTimeUse> <saml2:OneTimeUse/> </saml2:OneTimeUse> </saml2:Conditions> A similar situation takes place when attempting to set the DoNotCacheCondition for a SAML 1.1 token.
Problem conclusion
The code erroneously enclosed a duplicate OneTimeUse and DoNotCacheCondition inside the condition itself. This code fix removes the code that added the duplicate entry. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.17. 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
PM27388
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
2010-11-24
Closed date
2010-12-17
Last modified date
2011-06-09
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