Full User Name Support
The Integrity Lifecycle Manager server supports full user names on LDAP-compliant security realms and on MKS Domain. Once enabled, all Integrity Lifecycle Manager interfaces display full user names with the corresponding user IDs in brackets, for example, James Riley (jriley). In addition, all Integrity Lifecycle Manager user lists, Rational Application Developer integration with Integrity Lifecycle Manager, and Eclipse integration with Integrity Lifecycle Manager display full user names.
|
|
The Authorization Administration interface displays user IDs, not full user names.
|
If the full user name attribute is missing on the security realm or a user’s full user name entry is blank, client interfaces display the user ID.
Anywhere users need to log in or authenticate themselves, a user ID must be entered not the LDAP full user name. Similarly, to ensure users can be uniquely identified, the MKSSI_USER environment variable must contain the user ID, not the full user name.
Before you enable full user name support, note the following:
• Revisions locked at the time full user name support is enabled do not display full user names. When the revisions are unlocked then relocked, full user names display.
• Long text fields containing data prior to the time full user name support is enabled display only user IDs and not full user names. Any additions to the fields after the feature is enabled include full user names.
• If you are using an LDAP-compliant security realm, you cannot edit full user names in the Integrity Lifecycle Manager administration client. Instead, edit full user names in the LDAP security realm.
• If you are using the MKS Domain security realm, you can edit full user names. You need to refresh your users and groups to see your changes in Integrity Lifecycle Manager. For more information on working with the MKS Domain, see the Integrity Lifecycle Manager Installation and Upgrading Guide.
