Configuring a Remote Crowd Directory
Two things need to be done in order to configure the local Crowd server to obtain users and groups from a remote Crowd server:
- The local Crowd server needs to be given access to the remote Crowd server. This is achieved by adding a new application on the remote Crowd server.
- The new Remote Crowd directory needs to be added to the local Crowd server with details on how to connect to the remote Crowd server.
In our local testing, we found that it took about 4 minutes to sync to external Crowd with 10 000 users, 1 000 groups, and 200 000 memberships.
Roles are not supported in Remote Crowd Directories.
To configure a Remote Crowd directory:
- Log in to the Crowd Administration Console on the remote Crowd server.
- Add a new application which will be the local Crowd server. The application name and password entered here will be used later by the local Crowd server to connect to the remote Crowd server.
- Log in to the Crowd Administration Console on the local Crowd server.
- In the top navigation bar, click Directories.
- In the left-hand menu, click Add Directory.
- Select Remote Crowd, and click Next.
- Enter the name and the description.
We recommend that you leave 'Cache Enabled' at its default setting (enabled). Remote Crowd directory caching works the same way as it does for LDAP directories. For more information, see Configuring Caching for an LDAP Directory.
- Click the Connection tab. See screenshot 2 below.
- Fill in the basic connection information for your remote Crowd server.
- Click Test Connection to verify that Crowd can successfully connect to the directory.
- Click the Permissions tab to configure the directory's permissions.
Configuring Directory Details
Screenshot 1: Directory details
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:
We recommend that you turn on caching. Remote Crowd directory caching works the same way as it does for LDAP directories. For more information, see Configuring Caching for an LDAP Directory.
Use Nested Groups
Enable or disable support for nested groups on the Remote Crowd directory.
Configuring Connection Details
Screenshot 2: Connection details
The connection URL to use when connecting to the directory server. The URL should be in the following format:
Application name used to authenticate to the remote Crowd server.
Application password used to authenticate to the remote Crowd server.
The time, in seconds, to wait for a connection to be established. If there is no connection within the specified time period, the connection attempt will be aborted. A value of 0 (zero) means there is no limit.
The maximum number of simultaneous connections to remote Crowd server.
HTTP proxy server domain name. This field is required if the remote Crowd server is behind a HTTP proxy.
HTTP proxy server port number. This field is required if the remote Crowd server is behind a HTTP proxy.
HTTP proxy server username. This field is required if the HTTP proxy server requires authentication.
HTTP proxy server password. This field is required if the HTTP proxy server requires authentication.
|Enable Incremental Sync||We recommend that you turn on incremental synchronization. It will cause only changes since the last synchronization to be queried when synchronizing, thus significantly reducing synchronization resource usage.|
Crowd will synchronize with the remote Crowd server every x minutes, where 'x' is the number specified here. Remote Crowd directory caching works the same way as it does for LDAP directories, for which there is more information in Configuring Caching for an LDAP Directory.
Specify the directory permissions, which allow you to restrict the way in which applications can use the directories. See Specifying Directory Permissions.
Once you have configured the directory's permissions, you have finished configuring your new directory. You can then map the directory to the appropriate applications.
- Using the Directory Browser
- Adding a Directory
- Configuring an Internal Directory
- Configuring an LDAP Directory Connector
- Configuring a Remote Crowd Directory
- Configuring a Custom Directory Connector
- Configuring a Delegated Authentication Directory
- Configuring Azure Active Directory
- Configuring Caching for an LDAP Directory
- Using Naive DN Matching
- Specifying Directory Permissions
- Importing Users from Atlassian Confluence
- Importing Users from Atlassian Jira
- Importing Users from Atlassian Bamboo
- Importing Users from Jive Forums
- Importing Users from CSV Files
- Importing Users from One Crowd Directory into Another
- Configuring directories for failover authentication