Fix (APAR): PK74487
Status: Fix
Release: 7.0.0.1,7.0,6.1.0.19,6.1.0.21
Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows
Supersedes Fixes:
CMVC Defect: PK74487
Byte size of APAR: 83013
Date: 2008-11-07
Abstract: More than one disjunct searchBases in one repository broke the multiple realms search.
Description/symptom of problem:
PK74487 resolves the following problem:
ERROR DESCRIPTION:?
In an LDAP configuration which has two base
entries, only one of the base entries is used in a realm.
When searching for a user in that realm, users belonging to
the other base entry are returned as well.
LOCAL FIX:?
PROBLEM SUMMARY:?
USERS AFFECTED:
All users of WebSphere Application Server
V6.1 and V7.0 who use the federated
repositories (Virtual Member Manager).
PROBLEM DESCRIPTION:
More than one disjunct searchBases
in one repository broke the multiple
realms search.
RECOMMENDATION:
None
Multiple searchBases with no overlap relationship in one
repository caused the entities the do not belong to the realm
to be returned in multiple realms search.
For example, there are the following two disjunct searchBases
for one LDAP repository,
realmA has participatingBaseEntries 'dc=com'.
When search with realmA specified, entities under baseEntries
'dc=yourco' would also be returned.
PROBLEM CONCLUSION:?
The problem has been fixed. The entities that do not belong to
the realm will not be returned in multiple realms search.
The fix for this APAR is currently targeted for inclusion in
fixpacks 6.1.0.23 and 7.0.0.3. Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Directions to apply fix:
Fix applies to Editions:
Release 6.1, 7.0
x_ Application Server (Express or BASE)
x_ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
x_ 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.
* For 6.1, be at V6.1.0.13 or newer of the Update Installer.
* For 7.0, be at V7.0.0.0 or newer of the Update Installer.
Please note that 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.19-WS-WAS-IFPK12345.pak) or a single file with a .zip extension (such as 6.1.0.19-WS-WAS-IFPK12345.zip) which then contains one or more files with a .pak extension.
The following files are included in this fix. Please choose the appropriate one:
6.1.0.19-WS-WAS-IFPK74487.pak - Supports fixpack 6.1.0.19
6.1.0.21-WS-WAS-IFPK74487.pak - Supports fixpack 6.1.0.21
7.0.0.0-WS-WAS-IFPK74487.pak - Supports fixpack 7.0.0.0 and 7.0.0.1
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 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 (6.1.0.19-WS-WAS-IFPK74487.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: