Fixes are available
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 self-issuing a SAML token, in order to put the Subject in an AuthenticationStatement, you must call the API requesterData.setAuthenticationMethod(authMethod). There is no equivalent of this API on the SAML callback handler so it can only produce self-issued tokens with the Subject in an AttributeStatement.
Local fix
Local Fix￘ n-a
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server * * administrators of WS-Security enabled * * JAX-WS applications and SAML * **************************************************************** * PROBLEM DESCRIPTION: You cannot create a self-issued SAML * * token with AuthenticationStatement * * using callback handler * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this * * APAR. * **************************************************************** When the WS-Security runtime creates a self-issued SAML token, by default, the Subject element is containted within an AttributeStatement. For example: <AttributeStatement> <Subject> <NameIdentifier>user1</NameIdentifier> <SubjectConfirmation> <ConfirmationMethod>urn:oasis:names:tc:1.0:cm:sender- vouches</Co nfirmationMethod> </SubjectConfirmation> </Subject> </AttributeStatement> You can also create the Subject element within an AuthenticationStatement. For example: <AuthenticationStatement AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:password"> <Subject> <NameIdentifier>user1</saml:NameIdentifier> <SubjectConfirmation> <ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender- vouche s</ConfirmationMethod> </SubjectConfirmation> </Subject> </AuthenticationStatement> However, if you want to create the Subject element in an AuthenticationStatement, the only way that you can do it is with the API requesterData.setAuthenticationMethod(authMethod). You can only produce an AttributeStatement when using SAMLGenerateLoginModule and callback handler settings to self-issue the SAML token.
Problem conclusion
The switch for using an AuthenticationStatement rather than an AttributeStatement in a self-issued SAML token is by setting the AuthenticationMethod. Setting the AuthenticationMethod is only exposed through the APIs; it is not exposed in the SAMLGenerateCallbackHandler. Because of this, if you are creating a self-issued SAML token using the callback handler, you cannot create a token with an AuthenticationStatement. The WS-Security runtime is updated to expose setting the AuthenticationMethod in the SAMLGenerateCallbackHandler. The following custom property is added to SAMLGenerateCallbackHandler: authenticationMethod=(method) When this property is set, the Subject element will be put in an AuthenticationStatement instead of an AttributeStatement. Also, the value for AuthenticationMethod attribute on the AuthenticationStatement element will be set to the value for the custom property. For instance, if the authenticationMethod property is set as follows for a self-issued SAML sender-vouches token: authenticationMethod=urn:oasis:names:tc:SAML:1.0:am:unspecified An AuthenticationStatement similar to the following will be created: <AuthenticationStatement AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:unspecified "> <Subject> <NameIdentifier>user1</saml:NameIdentifier> <SubjectConfirmation> <ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouche s</ConfirmationMethod> </SubjectConfirmation> </Subject> </AuthenticationStatement> 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
Temporary fix
Comments
APAR Information
APAR number
PM69342
Reported component name
WAS WEB 2.0 FEA
Reported component ID
5724J0852
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-07-20
Closed date
2012-08-02
Last modified date
2012-08-02
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