Health Check: Internal Administrator User

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Purpose

This health check scans your current user directories to determine if there is an internal administrator available. When Confluence is set up for the first time, a local administrative account is created - separate from any LDAP or external user management that is set up. In the event that external user management is inaccessible, this user account allows administrative access to the instance.

Understanding the Results

Healthy status if the internal directory exists, the directory have at least 1 admin user, Confluence is not configured to use SSO.

The Health Check has passed and your Internal Admin user is configured according to best practices.

Confluence is configured to use Crowd SSO.

The Health Check has passed because the environment uses SSO technologies.


Confluence internal user directory does not exist or is disabled.

This environment does not have an active Internal User Directory, or it is not active. See the Configuring User Directories user guide for instructions on creating a new User Directory or alternatively review instructions to activate your Internal Directory if your Internal User Directory is disabled.

Confluence has an enabled internal user directory, however, there are no users in this directory.

The Internal User directory does not contain any users. Create an Admin User within this user directory by following the steps in Add users and set permission 

Confluence has an enabled internal user directory, however, it's administrator user does not exist or is disabled.

The Health Check has failed to detect a user with enough permissions to quickly gain access to the environment in the event of an External User Directory failure. Create an Admin User within this user directory. See Manage Users.

Confluence wasn't able to access the directory with the ID <ID> - see the application log for more details.

Please check that:

  1. Any SSO solution in use is configured correctly.
  2. All Add-ons installed are compatible.
  3. Your version of Confluence is not End of Life.

Otherwise, please Create a Support Zip and contact Atlassian Support for further assistance with this error.

Confluence wasn't able to find the directory with the ID <ID> - see the application log for more details.

Please check that:

  1. Any SSO solution in use is configured correctly.
  2. All Add-ons installed are compatible.
  3. Your version of Confluence is not End of Life.

Otherwise, please Create a Support Zip and contact Atlassian Support for further assistance with this error.

Resolution

Atlassian recommends never making changes to the internal directory once initially configured. Keeping a local administrative account available helps to ensure Confluence is always accessible.

For this check to pass Confluence will need to be using an SSO solution or: 

  1. An Internal User Directory that is active.
  2. A System Admin User in that Internal Directory.

An additional System Admin user will consume additional user license in Confluence.

DescriptionThis health check scans your current user directories to determine if there is an internal administrator available. When Confluence is set up for the first time, a local administrative account is created - separate from any LDAP or external user management that is set up. In the event that external user management is inaccessible, this user account allows administrative access to the instance.
ProductConfluence
PlatformServer
Last modified on Mar 3, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.