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 new function.
Error description
A fully-formed SAML token can be can be put in the sharedState by a login module and the SAMLGenerateLoginModule will use that token as if it were built by itself. This allows the SAML token generator to send tokens built dynamically by a stacked login module. There is no method for this same kind of customization with the LTPA token generator. The username and password must be hardcoded in the LTPA token callback handler. If the username and password needs to be set dynamically, or if you want to set the LTPA token bytes yourself, there is no way to do this.
Local fix
use an alternative Base64 encoding implementation
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server * * developers of WS-Security enabled JAX-WS * * applications * **************************************************************** * PROBLEM DESCRIPTION: The WS-Security token generator cannot * * accept an application specified * * username and password * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this * * APAR. * **************************************************************** A fully-formed SAML token can be can be put in the sharedState by a login module and the SAMLGenerateLoginModule will use that token as if it were built by itself. This allows an application developer to build SAML tokens dynamically instead of having to use hardcoded values in the callback handler. Although you can dynamically pass a username and password to the LTPAGenerateLoginModule when using WSSAPIs, if you must use policy sets and bindings, there is no way to pass dynamic information to the LTPA token generator.
Problem conclusion
The WS-Security runtime is updated to allow an application developer to either dynamically set the username and password that the LTPAGenerateLoginModule uses when generating a token or set the token bytes absolutely. Setting the token bytes is useful when an application developer wants to write code to obtain the LTPA token from the HTTP header of an inbound request, then send it out in the Security header of an outbound SOAP message. Useful methods for obtaining the inbound HTTP headers and Base64 encoding/decoding are provided on APAR PM70833. Three new methods are added to com.ibm.websphere.wssecurity.wssapi.token.GenericSecurityTokenFa ctory UsernameToken getSimpleUsernameToken(String username); UsernameToken getSimpleUsernameToken(String username, char[] password); BinarySecurityToken getSimpleBinarySecurityToken(Class tokenClass, byte[] binary) throws WSSException; An application developer can pass custom data to the LTPAGenerateLoginModule in two ways in this priority order: 1) From the sharedState from a stacked JAAS login module 2) From the com.ibm.wsspi.wssecurity.token.tokenHolder list on the message context Refer to the following constants in com.ibm.wsspi.wssecurity.core.Constants for more information: com.ibm.wsspi.wssecurity.token.tokenHolder com.ibm.wsspi.wssecurity.token.enableCaptureTokenContext An application developer can change the username and password that is used by LTPAGenerateLoginModule when generating an LTPA token. When a simple UsernameToken has been provided for use by LTPAGenerateLoginModule, it will override what is configured in the callback handler. Following is an example of code that would go in a stacked login module in the login() method to override the username and password. _sharedState comes from the first Map parameter on the initialize method in the login module. import com.ibm.websphere.wssecurity.wssapi.token.GenericSecurityTokenFa ctory; import com.ibm.websphere.wssecurity.wssapi.token.UsernameToken; public boolean login() throws LoginException { //get the factory GenericSecurityTokenFactory factory = GenericSecurityTokenFactory.getInstance(); UsernameToken unt = factory.getSimpleUsernameToken("username", "password".toCharArray()); factory.putGeneratorTokenToSharedState(_sharedState, unt); return true; } Following is an example of code that can be used to set the token bytes: import com.ibm.websphere.wssecurity.wssapi.token.GenericSecurityTokenFa ctory; public boolean login() throws LoginException { //get the factory GenericSecurityTokenFactory factory = GenericSecurityTokenFactory.getInstance(); byte [] tokenBytes = getTokenBytes();//method implemented by you BinarySecurityToken bst = factory.getSimpleBinarySecurityToken(com.ibm.websphere.wssecurit y.wssapi.token.LTPAv2Token, tokenBytes); factory.putGeneratorTokenToSharedState(_sharedState, bst); return true; } LTPAConsumeLoginModule has also been updated so that an LTPA token that is consumed is available on the shared state for use by a stacked login module. The token can be obtained with the following method from the GenericSecurityTokenFactory: SecurityToken token = getConsumerTokenFromSharedState(_sharedState, com.ibm.websphere.wssecurity.wssapi.token.LTPAv2Token.ValueType) ; Note that the valueType specified should correspond to the valueType of the LTPA token that is configured. If it does not, no token will be returned. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.27, 8.0.0.6, 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
PM70805
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-13
Closed date
2012-10-15
Last modified date
2012-10-15
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:
29 October 2021