PK44051: THE MEMBER FIXER MODULE CAN NOT UPDATE USER DNS FROM DIFFERENT B RANCHES

APAR status

• Closed as program error.

Error description

• The LDAP repository WCM uses may be configured to use multiple
  branches (or organizational units) in a single realm where
  different users can exist, for example:
  
  cn=John Smith,ou=Portal,o=IBM
  cn=Joan Stevens,ou=WCM,o=IBM
  
  If the user DNs change for any reason (e.g. a user or
  organization unit changes name), the member fixer module can not
  be used to update the user references in WCM items because it
  currently does not support updating users under multiple
  branches.
  

Local fix

Problem summary

• The member fixer module was constructing the new DNs based off
  the configured values in the wpconfig.properties file which only
  allowed for a single user suffix to be specified.
  Affected users all version 6x users up to version 6.0.1.1 the
  code fix is included in version 6.0.1.1 but you must use the
  instructions in the readme of the fix to use the fix even on
  6.0.1.1.
  

Problem conclusion

• After the fix for this issue is applied or if it is included in
  your current version such as 6.0.1.1 you must edit the
  WCMConfigService.properties file with mappings to your existing
  DNs:
  The member fixer module's "alt_dn" mode now checks for mapped
  alternate DNs in the WCMConfigServices.properties file before
  using the configured values in the wpconfig.properties file.
  You should perform the following steps to map user and group
  DNs in the WCMConfigServices.properties file before running
  the member fixer module:
  User and group DN syntax changes should be mapped in the
  PortalServer\wcm\shared\app\config\wcmservices\
  WCMConfigServices.properties file like so:
  EXISTING_DN_KEY=NEW_DN_SYNTAX
  where:
  EXISTING_DN_KEY is the key constructed from the existing DN
  by replacing all equals characters "=" and spaces " " with
  underscores "_" and using the string " ID " in place of the
  user's or groups id/common name.
  NEW_DN_SYNTAX is the replacement DN syntax where the user's
  or groups id/common name has been replaced with the string
  " ID ".
  For example, if you have a user branch with the following
  DN syntax:
  cn=John Smith,ou=Portal Users,o=IBM
  You construct the EXISTING_DN_KEY by replacing all "=" and " "
  with "_" in the DN, and the user id, in this case "John Smith"
  with " ID ", so in this example the EXISTING_DN_KEY will be:
  cn_ ID ,ou_Portal_Users,o_IBM
  If you are changing the syntax of this branch to:
  cn=John Smith,ou=Portal,o=IBM
  The NEW_DN_SYNTAX will be the new DN with the user id, in
  this case "John Smith" replaced with
  " ID ", i.e: cn= ID ,ou=Portal,o=IBM
  This gives you the following mapping entry in your
  WCMConfigServices.properties file:
  cn_ ID ,ou_Portal_Users,o_IBM=cn= ID ,ou=Portal,o=IBM
  You can of course have several mapping entries for
  different user and group branches, i.e:
  cn_ ID ,ou_Portal_Users,o_IBM=cn= ID ,ou=Portal,o=IBM
  You could then run the member fixer as normal using the
   alt_dn option:
  http:// HOST : PORT /wps/wcm/connect?MOD=MemberFixer&
  library= LIBRARY_NAME &alt_dn=UPDATE&fix=true
  An additional option has also been added to the module so
  that user references can be updated in items without
  affecting the items last modified date. Add
  "&preserve_dates=true" to the URL to run member fixer in
   the mode.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• WCM
  

Fix information

• Fixed component name

  WRKPLC WEB CON

• Fixed component ID

  5724I2900

Applicable component levels

• R60A PSY

     UP