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,
|
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:
| |
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-SECURITY' in order to ensure password compatibility. | |
Use Nested Groups | Enable or disable support for nested groups on the internal user directory. |
See Specifying Directory Permissions.