Documentation for Crowd 2.5. Documentation for other versions of Crowd is available too.

Custom directory connectors allow developers to connect Crowd to custom user-stores, such as existing databases or legacy systems.

First you need to create a custom directory connector. The simplest way to accomplish this is to add a JAR file with the necessary classes to the Crowd WEB-INF/lib folder. For details, please see Creating a Custom Directory Connector​.

Once you have added your JAR file to the Crowd WEB-INF/lib folder, you are ready to configure a Custom Directory Connector, as described below.

To configure a Custom Directory Connector,

  1. Log in to the Crowd Administration Console.
  2. Click the 'Directories' link in the top navigation bar.
  3. This will display the Directory Browser. Click the 'Add Directory' link.
  4. Click the 'Custom' button.
  5. Complete the fields as described in the table below.
  6. Click the 'Continue' button to configure the directory's permissions.

(info) Once you have configured the directory's permissions, you will have finished configuring your new directory. You can then map the directory to appropriate applications.

Screenshot: 'Create Custom Directory'





Custom Directory Store Attributes

説明

名前

The name used to identify the directory within Crowd. This is useful when there are multiple directories configured, e.g. Chicago Employees or Web Customers.

説明

Details about this specific directory.

アクティブ

Only deselect this if you wish to prevent all users within the directory from accessing all mapped applications. If a directory is not marked as 'Active', it is inactive. Inactive directories:

  • are not included when searching for users, groups or memberships.
  • are still displayed in the Crowd Administration Console screens.

実装クラス

Implementation of com.atlassian.crowd.integration.directory.RemoteDirectory Java interface. Must be in the Crowd CLASSPATH.

Next Step:

See Specifying Directory Permissions 

関連トピック

Crowd Documentation



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.