A single user can have different usernames in different applications. These different usernames are called 'aliases'. As a Crowd administrator, you can manage each user's aliases for the applications the user is authorised to access.
On this page:
Enabling User Aliasing for an Application
You can choose to enable or disable aliasing for each application. By default, user aliasing is disabled.
User aliasing can reduce the performance of your user directory, especially on user searches.
To enable user aliasing for an application,
Screenshot: Application options
Specifying a User's Aliases
You can add and remove aliases via the user management screens in the Crowd Administration Console.
To edit a user's aliases,
Screenshot: Specifying a user's aliases
Examples and Use Cases
- Using Crowd, you can link a number of usernames as aliases of Arthur's primary login ID.
- Arthur can log in just once, to any Crowd-connected application. He will be automatically logged into the other applications via single sign-on (SSO).
- When logging in to a specific application (e.g. Confluence), Arthur must use the specific username (alias) for that application, e.g. 'arthur'.
- When logging in to Crowd, Arthur must use his primary login i.e. the one in the directory, e.g. 'adent'.
Here are some cases where Crowd's user aliasing may be useful:
- Aliasing allows you to work around the problem that occurs when you want to implement a single user base for a number of existing systems, where users may have different usernames in each system.
- When someone gets married or changes their name, you may wish to rename a user in your LDAP directory, such as Microsoft Active Directory. To avoid problems in applications which do not allow user renaming, you can now link the new LDAP username to an alias in Crowd.
- Some systems may use email addresses as usernames, while in others this may expose users to email spambots. Using Crowd aliasing, you can use different username formats to suit your application requirements.