2. Managing Directories

Crowd supports an unlimited number of user directories. A directory can either be internal to Crowd, or connected to Crowd via an LDAP connector (e.g. for Active Directory) or via a custom directory connector (e.g. for a legacy database).

Once a directory has been defined in Crowd, it can be mapped to applications. Crowd will then delegate authentication and authorisation requests to the directory, for all applications that are mapped to that directory. Modification of directory entities (users, groups and roles) 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.

• 2.1 Using the Directory Browser
• 2.2 Adding a Directory
  • 2.2.1 Configuring an Internal Directory
  • 2.2.2 Configuring an LDAP Directory Connector
    • 2.2.2.1 Microsoft Active Directory
      • Configuring an SSL Certificate for Microsoft Active Directory
    • 2.2.2.2 SunONE
    • 2.2.2.3 OpenLDAP
    • 2.2.2.4 Apache Directory Server (ApacheDS)
    • 2.2.2.5 Generic LDAP Directories
  • 2.2.3 Configuring a Custom Directory Connector
• 2.3 Specifying Directory Permissions
• 2.4 Importing Principals and Groups into a Directory
  • 2.4.1 Importing Users from Atlassian Confluence
  • 2.4.2 Importing Users from Atlassian JIRA
  • 2.4.3 Importing Users from Jive Forums
  • 2.4.4 Importing Users from CSV Files
    • 2.4.4.1 Configuring the CSV Importer
    • 2.4.4.2 Mapping CSV Fields to Crowd Fields
    • 2.4.4.3 Confirming the CSV Importer Configuration
    • 2.4.4.4 Viewing the Results of the Import