Fix (APAR): PK95461 Status: Fix Release: 6.1.0.25,7.0.0.5 Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 6.1.0.25: 38297 7.0.0.5: 46975 Date: 6.1.0.25: 2009-09-30 7.0.0.5: 2009-09-29 Abstract: If a j_security_check request URI includes additional servlet path data and filters are mapped to the servlet path, the filters are not called. Description/symptom of problem: PK95461 resolves the following problem: ERROR DESCRIPTION: On fix pack 6.1.0.25 when application security is enabled, a login screen is displayed to access ITCAM. After the user enters and submits login details a new empty login creen is displayed. As a reult it is not possible to access ITCAM. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: IBM WebSphere Application Server Version 6.1.0.25 and 7.0.0.5 users. PROBLEM DESCRIPTION: If a j_security_check request URI includes additional servlet path data and filters are mapped to the servlet path, the filters are not called. RECOMMENDATION: None As a result of PK79894, a filter for a j_security_check request will only be called if the filter mapping matches to "/j_security_check". This is problematic if, for example, the j_security _check request specifies a URI relative to the context root of "/path/j_security_check" and filters specify a mapping which requires "/path" to result in a match. The same issue exists for "ibm_security_logout" requests. Note that IBM Tivoli Composite Application Manager (ITCAM) relies on such a filter mapping and as a result its filters are not called for a j_security_check request after PK79894. This causes a login failure and re-display of an empty login screen. PROBLEM CONCLUSION: The WebContainer has been modified so that the URI relative to the context root of a j_security_check request is used when mapping a request to filters. This restores the behavior of the WebContainer in this respect to pre PK79894 behavior. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.27 and 7.0.0.7. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply the fix to release 7.0: Fix applies to Editions: Release: 7.0 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 environment. * Be Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V7.0.0.0 or later of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateInstaller/version.txt. However it is highly recommended to use the latest version of Update Installer for IBM WebSphere Application Server Version 7 which can be downnloaded from the link specified below. The update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg24020448 For detailed instructions on how to extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006162 1) Copy the supplied .pak file directly to the maintenance directory. 2) Shutdown WebSphere. Manually execute setupCmdLine.bat in Windows or ../setupCmdLine.sh in UNIX from the WebSphere instance that maintenance is being applied to. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Launch the 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 (the .pak file which was copied into the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere. Directions to apply fix on release 6.1: Fix applies to Editions: Release 6 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.1.0.13 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. 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.ibm.com/support/docview.wss?rs=180&uid=swg21205400 Note that there are two different methods for delivering iFixes, depending on the contents. The fix may be delivered either as a single file with a .pak extension (such as 6.1.0.11-WS-WAS-IFPK12345.pak) or a single file with a .zip extension (such as 6.1.0.11-WS-WAS-IFPK12345.zip) which then contains one or more files with a .pak extension. 1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into the maintenance directory. 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 and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. 8) Please note that in the future, if a Feature Pack is installed or uninstalled, a different set of iFixes will be needed. Use the Update Installer again at that time, with the maintenance directory location where these maintenance packages are stored, to determine the required interim fixes for the new WebSphere and Feature Pack(s) combination. 9) The maintenance packages could have one of a set of names, and these names will help determine which maintenance package you need to install. The APAR name (PKxxxxx) should appear as part of the filename. Between the APAR number and the .pak extension there will be 0 to 2 characters added. The table below indicates the usage of each of the maintenance packages with respect to which Feature Packs, if any, are installed. |.pak File Names |No Feature Packs|EJB3 Only|WebServices Only| Both | |6.1.0.x-WS-WAS-IFPK12345 | X | X | X | X | |6.1.0.x-WS-WAS-IFPK12345C | X | | | | |6.1.0.x-WS-WAS-IFPK12345CE | | X | X | X | |6.1.0.x-WS-WAS-IFPK12345W | X | X | | | |6.1.0.x-WS-WAS-IFPK12345WE | | | X | X | |6.1.0.x-WS-WAS-IFPK12345E | X | | X | | |6.1.0.x-WS-WAS-IFPK12345EE | | X | | X | 10) Restart WebSphere Directions to remove the fix from releases 6.1 and 7.0: 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) Select file name of the maintenance package to uninstall (for example, 6.1.0.11-WS-WAS-IFPK12345.pak). 6) Verify the Uninstallation Summary and continue with the uninstall. 7) Restart WebSphere Directions to re-apply fix releases 6.1 and 7.0: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: