ADMINISTERING
When you rename a web user who has a vaulted ID, for example, an HCL Verse user, the steps to process the request occur automatically.
After you initiate the rename request, the following steps occur to process the request. Without AdminQ, the rename requires a web user to authenticate with Domino using an HCL Notes client.
Note: The servers involved in processing the request must run at least Domino 12.0.1.
1. You rename a user which generates a "Initiate Rename in Domino Directory" request in admin4.nsf.
2. When the "Delete Obsolete Change Requests" request runs each night, AdminP searches the Domino directory for unexpired "Initiate Rename in Domino Directory" requests. These requests are generated immediately after a rename request and indicate that the user whose name is being changed has not authenticated with Domino from the Notes client to kick off the rename processing.
3. When AdminQ finds an unexpired "Initiate Rename in Domino Directory" request, it creates a "UserRename" request for the user being renamed in adminq.nsf and sets its state to "Needs processing."
4. The UserRename request replicates to adminq.nsf on the ID vault administration server for the vault with the user ID.
5. AdminQ on the ID vault administration server finds the request in the state "Needs Processing" and updates the associated user ID in the ID vault. This takes the place of the user logging in with the Notes client and causing the ID file to synchronize with the ID vault.
6. After the ID is updated in the ID vault, AdminQ changes the state of the entry in adminq.nsf to "Processed."
7. AdminQ on the vault administration server generates a "Rename Person in Domino Directory"request in admin4.nsf.
8. The "Rename Person in Domino Directory" request replicates to admin4.nsf on the domain administration server.
9. AdminP on the domain administration server kicks off the usual rename request flow.
Related tasks Using AdminQ to process web user requests
Related reference Rename person