Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-45245

Internal administrator health check failing possibly due to high number of internal directory users

XMLWordPrintable

      Summary

      The internal administrator health check throws a false negative, most likely due to a high number of users in the internal directory.

      Environment

      An instance with a large number of users, e.g.: 17,000 or so.

      Steps to Reproduce

      1. Startup Confluence with latest Confluence Instance Health.
      2. Ensure there are local admin users setup.
      3. Browse to the instance health page.

      Expected Results

      The health check passes, there are local admin users configured.

      Actual Results

      The health check fails, with a false positive.

      Notes

      I was able to reproduce this behavior by restoring a customer's backup. The internal directory, which is the only directory, contains 17,400+ users. The internal administrator health check fails, even though there are seven administrators set up, either through confluence-administrators membership or explicit global permissions. After removing all but the seven administrators, the health check shows a green result as expected.

      Based on the code, the check works by loading up all of the internal directory users, and then iterating through the set to find administrators. There appears to be a maximum of 1000 set on the user entity query. Could this indeed be causing the false negative?

      Temporary Workaround until bug is fixed

      1. Go to > Add-ons
      2. Click to expand the Confluence Healthcheck Plugin
      3. Click to expand the 29 of 29 modules on the right side
      4. Locate and disable the module named confluence.healthcheck.directory.internal.name (internalAdminCheck)

          Form Name

            [CONFSERVER-45245] Internal administrator health check failing possibly due to high number of internal directory users

            Katherine Yabut made changes -
            Workflow Original: JAC Bug Workflow v3 [ 2879746 ] New: CONFSERVER Bug Workflow v4 [ 3003520 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2798041 ] New: JAC Bug Workflow v3 [ 2879746 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow [ 2732263 ] New: JAC Bug Workflow v2 [ 2798041 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2380454 ] New: JAC Bug Workflow [ 2732263 ]
            Brian made changes -
            Description Original: h3. Summary

            The internal administrator health check throws a false negative, most likely due to a high number of users in the internal directory.

            h3. Environment

            An instance with a large number of users, e.g.: 17,000 or so.

            h3. Steps to Reproduce

            # Startup Confluence with latest Confluence Instance Health.
            # Ensure there are local admin users setup.
            # Browse to the instance health page.

            h3. Expected Results

            The health check passes, are there are local admin users configured.

            h3. Actual Results

            The health check fails, with a false positive.

            h3. Notes

            I was able to reproduce this behavior by restoring a customer's backup. The internal directory, which is the only directory, contains 17,400+ users. The internal administrator health check fails, even though there are seven administrators set up, either through _confluence-administrators_ membership or explicit global permissions. After removing all but the seven administrators, the health check shows a green result as expected.

            Based on the code, the check works by loading up all of the internal directory users, and then iterating through the set to find administrators. There appears to be a maximum of 1000 set on the user entity query. Could this indeed be causing the false negative?

            h4. Temporary Workaround until bug is fixed
            # Go to !https://confluence.atlassian.com/download/attachments/590259974/Cog.png! > *Add-ons*
            # Click to expand the *Confluence Healthcheck Plugin*
            # Click to expand the *29 of 29 modules* on the right side
            # Locate and *disable* the module named *confluence.healthcheck.directory.internal.name (internalAdminCheck)*             		New: h3. Summary

            The internal administrator health check throws a false negative, most likely due to a high number of users in the internal directory.
            h3. Environment

            An instance with a large number of users, e.g.: 17,000 or so.
            h3. Steps to Reproduce
             # Startup Confluence with latest Confluence Instance Health.
             # Ensure there are local admin users setup.
             # Browse to the instance health page.

            h3. Expected Results

            The health check passes, there are local admin users configured.
            h3. Actual Results

            The health check fails, with a false positive.
            h3. Notes

            I was able to reproduce this behavior by restoring a customer's backup. The internal directory, which is the only directory, contains 17,400+ users. The internal administrator health check fails, even though there are seven administrators set up, either through _confluence-administrators_ membership or explicit global permissions. After removing all but the seven administrators, the health check shows a green result as expected.

            Based on the code, the check works by loading up all of the internal directory users, and then iterating through the set to find administrators. There appears to be a maximum of 1000 set on the user entity query. Could this indeed be causing the false negative?
            h4. Temporary Workaround until bug is fixed
             # Go to !https://confluence.atlassian.com/download/attachments/590259974/Cog.png! > *Add-ons*
             # Click to expand the *Confluence Healthcheck Plugin*
             # Click to expand the *29 of 29 modules* on the right side
             # Locate and *disable* the module named *confluence.healthcheck.directory.internal.name (internalAdminCheck)*
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 [ 2282114 ] New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2380454 ]
            Michael Andreacchio made changes -
            UIS Original: 12
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2223005 ] New: Confluence Workflow - Public Facing - Restricted v5 [ 2282114 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2173015 ] New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2223005 ]

              isadykov Ilia (Inactive)
              btom1 Brian
              Affected customers:
              2 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: