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.

Limitations when Editing Directories

You cannot edit, disable or remove the directory your user belongs to. This precaution is designed to prevent administrators from locking themselves out of the application by changing the directory configuration in a way that prevents them logging in or removes their administration permissions.

This limitation applies to all directory types. For example:

  • You cannot disable the internal directory if your user is an internal user.
  • You cannot disable or remove an LDAP or a Crowd directory if your user comes from that directory.

In some situations, reordering the directories will change the directory that the current user comes from, if a user with the same username happens to exist in both. This behaviour can be used in some cases to create a copy of the existing configuration, move it to the top, then remove the old one. Note, however, that duplicate usernames are not a supported configuration.

You cannot remove the internal directory. This precaution aligns with the recommendation below that you always keep an administrator account active in the internal directory.

Recommendations

The recommended way to edit directory configurations is to log in as an internal user when making changes to external directory configuration.

(warning) We recommend that you keep either an administrator or system administrator user active in your internal directory for troubleshooting problems with your user directories.

  • No labels