Internal directories use the Crowd database to store user, group and role information. Internal directories are stored in Crowd's database server.
To configure an internal directory,
- Log in to the Crowd Administration Console.
- Click the 'Directories' tab in the top navigation bar.
- This will display the Directory Browser. Click 'Add Directory' in the left-hand menu.
- Click the 'Internal' button.
- Complete the fields as described in the table below.
- Click the 'Continue' button to configure the directory's permissions.
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 internal directory

Internal Directory Attributes |
Description |
|---|---|
Name |
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. |
Description |
Details about this specific directory. |
Active |
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:
|
Password Regex |
Regex pattern which new passwords will be validated against. The regular expression format used is the java.util.regex.Pattern. For example, for an alphanumeric password of at least 8 characters, you could use the pattern: [A-Za-z0-9]{8,} |
Maximum Invalid Password Attempts |
The maximum number of invalid password attempts before the authenticating account will be disabled. Enter 0 to disable this feature. |
Maximum Unchanged Password Days |
The number of days until the password must be changed. This value is in days, enter 0 to disable this feature. |
Password History Count |
The number of previous passwords to prevent the user from using. Enter 0 to disable this feature. |
Password Encryption |
If you wish to import users into this directory from another Atlassian product, specify 'ATLASSIAN-SHA1' in order to ensure password compatibility. |
Use Nested Groups |
Enable or disable support for nested groups on the internal user directory. |
Next Step
See Specifying Directory Permissions.
RELATED TOPICS
- 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 Caching for an LDAP Directory
- Using Naive DN Matching
- Specifying Directory Permissions
- Importing Users and Groups into a Directory







3 Comments
Hide/Show CommentsSep 29, 2009
Matthew Block
To do more complex password requirement checks, I've found using the regex lookahead functionality very useful. For example, the following regex will check..
Sep 08, 2010
Dennis Benzinger | hybris GmbH
What happens if a already existing password becomes invalid by setting one of the options (e.g. Password Regex or Maximum Unchanged Password Days)?
Sep 08, 2011
Tin Pham
Does Crowd's internal directory allow access to it via LDAP? Is it extensible with custom fields?
Add Comment