Fix (APAR):  PK60237

Status:  Fix

Release:  6.1.0.9,6.1.0.15,6.1.0.13,6.1.0.11

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK60237

Byte size of APAR:  33919

Date: 2008-02-13

Abstract:  Case sensitivity for properties in Virtual Member Manager (VMM) is inconsistent

Description/symptom of problem:  
PK60237 resolves the following problem:

ERROR DESCRIPTION:                                              
We have an attribute defined in VMM config as givenName.        
In LDAP, the attribute is named givenname. So the name is       
equals but not equalsIgnoreCase                                 
                                                                
The bahaviour of VMM for a get call is as follows:              
If the requested properties explicitly contains givenName, then 
the value for LDAPs givenname is returned. If the requested     
properties is *, then the value for LDAPs givenname is          
NOT returned.                                                   
                                                                
This bahaviour obviously is inconsistent. Either the value      
should be returned in both cases (that's what we would prefer)  
or it should not be returned at all.                            

LOCAL FIX:                                                      
NONE                                                            

PROBLEM SUMMARY

USERS AFFECTED:
Websphere Application Server version 6.1
users who use federated repositories
(virtual member manager).

PROBLEM DESCRIPTION:
Case sensitivity for properties in
Virtual Member Manager (VMM) is
inconsistent

RECOMMENDATION:
None

There is a property defined in VMM schema called 'givenName'.
In LDAP, the attribute is named 'givenname'.  They do not
match exactly.

When a request is made for this property using the get() API:
- if the requested property is 'givenName', then the LDAP
attribute 'givenname' is returned.
- if the requested property is '*', then the LDAP attribute
'givenname' is not returned.

This is an inconsistent behavior.  The correct behavior should
be to return the LDAP attribute in both cases.

PROBLEM CONCLUSION:                                             
The problem has been addressed so that the return behavior is   
consistent.                                                     
                                                                
This fix is targeted for fixpack 6.1.0.17.                      
Please refer to the recommended updates page for delivery       
information:                                                    
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27004980 


Directions to apply fix:  Fix applies to Editions:
Release 6.1
x_ Application Server (Express or BASE)
x_ Network Deployment (ND)
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.
* Be at V6.1.0.13 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file <was_root>/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 6.1.0.0-WS-WAS-IFPK60237.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.

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 (6.1.0.0-WS-WAS-IFPK60237.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 (6.1.0.0-WS-WAS-IFPK60237.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: