Mapping a Directory to an Application
Mapping a directory to an application defines the user-base for an application. Sometimes known as 'application provisioning', directory mappings determine which user stores will be used when authenticating and authorizing a user's access request. Read more about users and groups.
When you defined an application, you chose a default directory for that application to use. Crowd also allows you to map multiple directories to each application. This allows each of your applications to view multiple user directories as a single repository.
To map a directory to an application,
- Log in to the Crowd Administration Console.
- Click the Applications tab in the top navigation bar.
- Click View for the application you wish to map.
- Click the Directories tab.
- Select the new directory from the drop-down list and click Add.
- The new directory will be added to the bottom of the list of mapped directories. You can use the blue up-arrow or down-arrow to move a directory higher or lower in the order:
Why directory order is important - Now choose how group memberships are aggregated over the directories you've just mapped. Group memberships are used to determine authorization permissions. See Effective memberships with multiple directories for more information.
On the Directories tab check Aggregate group memberships across directories to use the 'aggregating membership' scheme. When the checkbox is clear 'non-aggregating membership' is used. - You now need to choose which users within the directory may authenticate against the application. You have two choices:
- To allow all users within the directory to authenticate against the application, change Allow all to Authenticate to True, then click Update.
OR: - To allow only specific groups of users within the directory to authenticate against the application, see Specifying which Groups can access an Application.
- To allow all users within the directory to authenticate against the application, change Allow all to Authenticate to True, then click Update.
- Next, you should define the application's ability to add or update users in the directory. Click the Permissions tab and set the directory permissions for the application.
Note that updates are handled differently, depending on the membership aggregation scheme you selected in step 7. See Directory update operations.
Screenshot: 'Application — Map Directories'
RELATED TOPICS
- Using the Application Browser
- Adding an Application
- Integrating Crowd with Atlassian Bamboo
- Integrating Crowd with Atlassian Confluence
- Integrating Crowd with Atlassian CrowdID
- Integrating Crowd with Atlassian Crucible
- Integrating Crowd with Atlassian FishEye
- Integrating Crowd with Atlassian JIRA
- Integrating Crowd with Atlassian Bitbucket Server
- Integrating Crowd with Acegi Security
- Integrating Crowd with Apache
- Disabling Previous Versions of the Crowd Apache Connector
- Installing the Crowd Apache Connector on CentOS Linux
- Installing the Crowd Apache Connector on Red Hat Enterprise Linux
- Installing the Crowd Apache Connector on Ubuntu Linux
- Installing the Crowd Apache Connector on Debian
- Installing the Crowd Apache Connector on Other UNIX-Like Systems
- Installing the Crowd Apache Connector on Windows
- Integrating Crowd with Jive Forums
- Integrating Crowd with Spring Security
- Integrating Crowd with Subversion
- Integrating Crowd with a Custom Application
- Integrating Crowd with Atlassian HipChat
- Configuring the Google Apps Connector
- Mapping a Directory to an Application
- Effective memberships with multiple directories
- Specifying an Application's Address or Hostname
- Testing a User's Login to an Application
- Enforcing Lower-Case Usernames and Groups for an Application
- Managing an Application's Session
- Deleting or Deactivating an Application
- Overview of SSO
- Configuring Options for an Application
Last modified on Sep 20, 2017
Powered by Confluence and Scroll Viewport.