Fixes are available
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.45: Java SDK 1.6 SR16 FP60 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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
APAR status
Closed as new function.
Error description
Allow signing of a self-issued SAML token using the SHA-2 signature algorithm. Although this is arelady supported, its use is only externalized through APIs. This option should be available through the SAMLIssuerConfig.properties file and WS-Security policy bindings.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server users of * * WS-Security enabled JAX-WS web services * * and SAML * **************************************************************** * PROBLEM DESCRIPTION: Expose properties to sign SAML token * * using SHA-2 signature algorithm * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this * * APAR. * **************************************************************** There is currently support to sign a SAML token using the SHA-2 signature algorithm, http://www.w3.org/2001/04/xmldsig-more#rsa-sha256. However, you can only do this using the WSS APIs. There needs to be a way to do this using the SAMLIsseuerConfig.properties file or the WS-Security policy bindings.
Problem conclusion
The WS-Security runtime is updated so that you can specify in the SAMLIssuerConfig.properties file or WS-Security policy bindings to use the SHA-2 signature algorithm when signing a SAML token. The following property is added to SAMLIssuerConfig.properties file: UseSha2ForSignature The following property is added to the WS-Security policy bindings and should be set in the SAML token generator callback handler. This property can only be used on WebSphere Application Server v8 and later. com.ibm.wsspi.wssecurity.saml.config.issuer.UseSha2ForSignature The values for these properties are true and false. They default to false. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.39, 8.0.0.11 and 8.5.5.6. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Keywords: IBMWL3WSS, WSSEC, SAMLWSSEC
Temporary fix
Comments
APAR Information
APAR number
PI33760
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-01-29
Closed date
2015-02-16
Last modified date
2015-09-24
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
11 January 2022