LO64713: OLD NOTES ID CAN STILL BE UPDATED TO NEW NAME AFTER EXPIRED DAYS IN RENAME PROCESS

APAR status

• Closed as fixed if next.

Error description

• When using the Adminp process to rename user, such as change the
  common
  name, there is an option to honor old name before expired day as
  following:
  
  By default, after the expired days, if still use the old Notes
  ID to login domino server, the Notes ID will not be updated to
  new name.
  And receive error message "You are not authorized to access that
  database" when attempt to access mail database.
  
  For now, the customer's case, after expired days, copy of old
  Notes ID can still be updated to new name when login server.
  
  In the user's Person document, find that the "AdminpOld*" fields
  are still present.
  By default, these fields are added to the user's Person document
  when
  the "Initiate Rename in Domino Directory" request is processed,
  
  and they are subsequently removed when the "Rename in Person
  Documents" request is processed.
  
  And also find that the "Name Change Request" under
  Administration in person document still shows as "Pending" other
  than "None".
  By default, after expired day, it will be changed from "Pending"
  to "None" after running of the request "Delete Obsolete Change
  Requests" in admin4.nsf.
  And the content of "Change Request" under Certificates should be
  removed.
  
  Check the request "Delete Obsolete Change Requests", it fails
  with the error message:
  Title: Path:; Name:
  (|(ChangeRequest=*)(NewMailClientUpdateFlag=*)(NewRoamStatUpdtFl
  =*)($AdminpOldWebNameExpires=*))): Error looking up name on LDAP
  Server; See server log for further details.
  
  In addition, customer does not use the parameter
  Name_Change_Expiration_Days in their server.
  

Local fix

• The current workaround is to clear "Change Request" field
  manually (in person document -- certificates -- Notes
  certificates).
  Then "Name change request" field (in person document --
  Administration) will be changed from Pending to None. And
  user can not use the old Notes ID again.
  

Problem summary

• This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# XXQU8MM9RM.
  This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

APAR Information

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

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

Fix information

Applicable component levels