Fix (APAR): PK49813 Status: Fix Release: 6.1.0.11,6.0.2.21,6.0.2.19,6.0.2.17 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 77219 Date: 2007-10-18 Abstract: While verifying LTPATokens, there is a possibility that a signature verific ation of LTPATokens fails under stressed environment. Description/symptom of problem: PK49813 resolves the following problem: ERROR DESCRIPTION: Under the situation that LTPATokens are constantly generated and verified very frequently. For example, 400 LTPATokens are generated or verified by multiple threads in a second, token validation or generation fail occasionally. When this condition happens, one of following exceptions will be observed in ffdc log: com.ibm.websphere.security.auth.InvalidTokenException: Invalid signature. at com.ibm.ws.security.ltpa.LTPAToken2.isValid(LTPAToken2.ja va(Compiled Code)) at com.ibm.ws.security.ltpa.LTPAToken2.getBytes(LTPAToken2.j ava(Compiled Code)) at com.ibm.ws.security.token.AbstractTokenImpl.getBytes(Abst ractTokenImpl.java(Compiled Code)) at com.ibm.ws.security.auth.distContextManagerImpl.processSu bjectForPropagationAfterLogin(distContextManagerImpl.java(Co mpiled Code)) com.ibm.websphere.security.auth.WSLoginFailedException: Token is null. at com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(L TPAServerObject.java(Compiled Code)) at com.ibm.ws.security.token.SingleSignonTokenImpl.initializ eToken(SingleSignonTokenImpl.java(Compiled Code)) at com.ibm.ws.security.server.lm.wsMapDefaultInboundLoginMod ule.login(wsMapDefaultInboundLoginModule.java(Compiled Code)) LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: IBM WebSphere Application Server versions 6.0.2 and 6.1 users who are enabling Global Security. PROBLEM DESCRIPTION: While verifying LTPATokens, there is a possibility that a signature verification of LTPATokens fails under stressed environment. RECOMMENDATION: None Signature generation code was causing this issue because it might generate an invalid signature data when multiple threads are generating signature data simultaneously. As a result, even if LTPAToken2 is valid, a WSLoginFailedException is thrown. PROBLEM CONCLUSION: With this fix, the signature generation code no longer be accessed concurrently. The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.23 and 6.1.0.13. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?uid=swg27004980 Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0, 6.1 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes _X_ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file directly to the maintenance directory For 6.0.2.17 and 6.0.2.19, please use 6.0.2.17-WS-WAS-IFPK49813.pak For 6.0.2.21, please use 6.0.2.21-WS-WAS-IFPK49813.pak For 6.1.0.11, please use 6.1.0.11-WS-WAS-IFPK49813.pak 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: