This documentation is not intended to be read independently of the JIRA and Confluence documentation.
Please refer to the JIRA Administrator's Guide or the Confluence Administrator's Guide instead of the documentation in this space.

An internal directory with LDAP authentication offers the features of an internal directory while allowing you to store and check users' passwords in LDAP only. Note that the 'internal directory with LDAP authentication' is separate from the default 'internal directory'. On LDAP, all that the application does is to check the password. The LDAP connection is read only. Every user in the internal directory with LDAP authentication must map to a user on LDAP, otherwise they cannot log in.

When to use this option: Choose this option if you want to set up a user and group configuration within your application that suits your needs, while checking your users' passwords against the corporate LDAP directory. This option also helps to avoid the performance issues that may result from downloading large numbers of groups from LDAP.

(warning) Note that the 'internal directory with LDAP authentication' is separate from the default 'internal directory'.  This results in group memberships not being recognized across different directories and will need to be re-added per directory.  Issues, filters, and dashboards are still recognized between directories.

  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.