When you map multiple directories to an application, you also need to define the directory order. This is important in case the same user exists in multiple directories. When a user attempts to access an application, Crowd will search the directories in the order you specified, and will use the credentials (password, etc) of the first occurrence of the user to validate the login attempt (see diagram below).
To specify the directory order,
- Log in to the Crowd Administration Console.
- Click the 'Applications' link in the top navigation bar.
- This will display the Application Browser. Click the 'View' link that corresponds to the application you wish to map.
- This will display the 'View Application' screen. Click the 'Directories' tab.
- This will display a list of directories that are currently mapped to the application. Use the blue up-arrow or down-arrow to move a directory higher or lower in the order:
(Note: in Crowd, users are known as principals.)
Screenshot: 'Application---Mapped Directories'
How it works
Let's assume that JIRA has been set up as a Crowd application, and has been mapped to two directories, 'Partners' and 'Customers', in that order (as shown in the above screenshot).
Here is what happens when a user attempts to log in to JIRA:
Gliffy 
When granting the principle access to an application, Crowd amalgamates the group memberships in the directories, as described in 4.07 Editing a Principal's Group and Role Membership.
Related Topics
- 3.1 Using the Application Browser
- 3.2 Adding an Application
- 3.2.01 Integrating Crowd with Apache
- 3.2.02 Integrating Crowd with Subversion
- 3.2.03 Integrating Crowd with Atlassian Confluence
- 3.2.04 Integrating Crowd with Atlassian CrowdID
- 3.2.05 Integrating Crowd with Atlassian FishEye
- 3.2.06 Integrating Crowd with Atlassian JIRA
- 3.2.07 Integrating Crowd with Jive Forums
- 3.2.08 Integrating Crowd with Atlassian Bamboo
- 3.2.09 Integrating Crowd with Acegi Security
- 3.2.10 Integrating Crowd with Atlassian Crucible
- 3.2.11 Integrating Crowd with a Custom Application
- 3.3 Mapping a Directory to an Application
- 3.4 Specifying which Groups can access an Application
- 3.5 Specifying an Application's Address or Hostname
- 3.6 Testing a User's Login to an Application
- 3.7 Managing an Application's Session
- 3.8 Deleting or Deactivating an Application
