System information

Identity Manager Resources Reference
Part Number 820-2952-10 Page 105
The SAP GUI uses a different method to perform the rename because it has access to non-public
APIs and to the SAP kernel. The following steps provide a high-level description of how the
adapter performs the rename operation:
1. Get the user information for the existing user.
2. Save the ALIAS attribute, if one exists.
3. Create the new user.
4. Set the Activity Groups on the new user. (If in CUA mode, get the old user's Activity
Groups)
5. Set the Profiles on the new user. (If in CUA mode, get the old user's Profiles.)
6. Get the old user's Personalization Data.
7. Set the new user's Personalization Data.
8. Delete the old user.
9. Set the Alias on the new user if one was set on the old user.
If an error occurs during steps 1-3, the operation fails immediately. If an error occurs during steps
4-7, the new user is deleted and the whole operation fails. (If the new user cannot be deleted, a
warning is placed into the WavesetResult). If an error occurs during steps 8-9, a warning is added to
the WavesetResult, but the operation succeeds.
The Rename operation requires that a new password be set on the new user. This is most easily
accomplished by customizing the Rename User Task to invoke the Change User Password Task.
Sun Java System Access Manager
• The procedure described in the “Policy Agent” section in the Sun Java System Access
Manager documentation is outdated. Use the following procedure instead.
1. From the Identity Manager Administrator Interface menu bar, select Security.
2. Click the Login tab.
3. Click the Manage Login Module Groups button, located at the bottom of the page.
4. Select the Login Module to modify. For example, select Default Identity System
ID/Pwd Login Module Group.
5. In the Assign Login Module select box, select Sun Access Manager Login Module or
Sun Access Manager Realm Login Module.