- Internal to Crowd.
- Connected to Crowd via an LDAP connector (e.g. for Active Directory), with all authentication and user/group management in LDAP.
- A Crowd internal directory for user/group management but with authentication delegated to LDAP (e.g. Active Directory).
- Connected via a custom directory connector (e.g. for a legacy database).
Once you have defined a directory in Crowd, you can map it to applications. Crowd will then pass authentication and authorization requests to the directory, for all applications that are mapped to that directory. Modification of directory entities (users and groups) can be done via the Crowd Administration Console or via the application, depending on the application's capabilities.
You can even map multiple directories to an application, providing the application with a single view of multiple directories in a specified order.
- 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