Mapping a Directory to an Application
Mapping a directory to an application defines the user-base for an application. Directory mappings determine which user directories 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:
- Crowd Administration Console にログインします。
- In the top navigation bar, click the Applications tab.
- Click View for the application you wish to map.
- Select the Directories & groups 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 drag & drop the newly created row to move a directory higher or lower in the order. Why is directory order important?
- In the Directories & groups tab, check Aggregate group memberships across directories. Learn more.
- Choose which users within the directory may authenticate against the application. Select one of the following:
- Allow all users within the directory to authenticate against the application:
- In the Actions column, click the meatballs icon and select Configure authentication.
- Enable the Allow all users from this directory to authenticate check box, and click Save.
- Allow only specific groups of users within the directory to authenticate against the application, see Specifying which Groups can access an Application.
- 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. See Directory update operations.
Screenshot: 'Application — Map Directories'
For each directory mapped to the application you can also define groups that users will be automatically assigned to, when they first log in to the application. See Automatically Assigning Users to Groups for more details.
- Using the Application Browser
- 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
- Configuring Caching for an Application
- Overview of SSO
- Configuring Options for an Application