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

Inspect permissions shows incorrect results for mixed-case groups or users

      Issue Summary

      Any users or groups with uppercase characters in the username/groupname are not shown as having permissions in the inspect permissions feature. Note that such usernames and group names can only be created using external directories.

      The error happens on initially loading the data at start-up, so any groups or users added during testing without a restart are ok until the cache reinitialisation.

      Steps to Reproduce

      When we add a group (Group1) from an external directory and give it permission to view a space, it works fine. It shows up in the inspect permissions table with an upper case G, and respects permissions updates.

      1. When we do something that triggers a cache reinit (eg, re-ordering user directories), Group1 now shows up in the table as group1 with a lower case g and no longer respects permission updates. 
      2. Try to give group1 permission to view a space and it doesn't show up in the table.

      Expected Results

      Permissions can be updated as per usual.

      Actual Results

      Permission update is not reflected

      Workaround

      None

            [CONFSERVER-59700] Inspect permissions shows incorrect results for mixed-case groups or users

            Michael Andreacchio made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 512961 ]
            Alex K made changes -
            Comment [ If you're running the Confluence 7.4 Enterprise release, a fix for this issue is now available in Confluence 7.4.5, which you can find in the [Download Archives| https://www.atlassian.com/software/confluence/download-archives].
            ]
            Alex K made changes -
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            set-jac-bot made changes -

            Minh Tran added a comment -

            A fix for this issue is available to Server and Data Center customers in Confluence 7.4.0
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            Minh Tran added a comment - A fix for this issue is available to Server and Data Center customers in Confluence 7.4.0 Upgrade now or check out the Release Notes to see what other issues are resolved.
            Bradley Hyde made changes -
            QA Demo Status Original: Not Done [ 14330 ] New: Done [ 14331 ]
            QA Kickoff Status Original: Not Done [ 14234 ] New: Done [ 14235 ]

            A fix for  this issue is available to Server and Data Center customers in Confluence 7.3.5

            Upgrade now or check out the Release Notes to see what other issues are resolved.

            James Whitehead added a comment - A fix for  this issue is available to Server and Data Center customers in Confluence 7.3.5 Upgrade now or check out the Release Notes  to see what other issues are resolved.
            James Whitehead made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Bradley Hyde made changes -
            Description Original: h3. Issue Summary
            Any users or groups with uppercase characters in the username/groupname are not shown as having permissions in the inspect permissions feature. Note that such usernames and group names can only be created using external directories.

            The error happens on initially loading the data at start-up, so any groups or users added during testing without a restart are ok until the cache reinitialisation.

            h3. Steps to Reproduce

            When we add a group (Group1) from an external directory and give it permission to view a space, it works fine and I couldn’t reproduce any issues. It shows up in the inspect permissions table with an upper case G, and respects permissions updates.
             # When we do something that triggers a cache reinit (eg, re-ordering directories), Group1 now shows up in the table as group1 with a lower case g and no longer respects permission updates. 
             # Try to give group1 permission to view a space and it doesn't show up in the table.

            h3. Expected Results

            Permissions can be updated as per usual.

            h3. Actual Results

             !screenshot-1.png|thumbnail!

            Permission update is not reflected

            h3. Workaround

            None
            New: h3. Issue Summary

            Any users or groups with uppercase characters in the username/groupname are not shown as having permissions in the inspect permissions feature. Note that such usernames and group names can only be created using external directories.

            The error happens on initially loading the data at start-up, so any groups or users added during testing without a restart are ok until the cache reinitialisation.
            h3. Steps to Reproduce

            When we add a group (Group1) from an external directory and give it permission to view a space, it works fine. It shows up in the inspect permissions table with an upper case G, and respects permissions updates.
             # When we do something that triggers a cache reinit (eg, re-ordering user directories), Group1 now shows up in the table as group1 with a lower case g and no longer respects permission updates. 
             # Try to give group1 permission to view a space and it doesn't show up in the table.

            h3. Expected Results

            Permissions can be updated as per usual.
            h3. Actual Results

            !screenshot-1.png|thumbnail!

            Permission update is not reflected
            h3. Workaround

            None
            Jen Marfell (Inactive) made changes -
            Fix Version/s New: 7.4.0 [ 91500 ]

              bhyde Bradley Hyde
              rrobins Rachel Robins
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: