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

"Not Permitted" page when members of confluence-administrators attempt to edit pages on which they do not have edit permission

      In Confluence 5.6.x, member of "confluence-administrators" group can click "Edit" button and start editing the page. They receive a "Not Permitted" page when "Save" button is clicked.

      If the "Close" button is clicked instead (to exit the editor without saving), a blank page will be returned instead.

      Steps to replicate

      1. Make User B as the member of confluence-administrators group
      2. User A creates a page and applies a restriction to a specific group
      3. User B is Not a member of that group but Is a Space Administrator for the space
      4. User B goes to the page and the edit function is enabled
      5. User B Clicks Edit and starts to make changes
      6. User B finishes making changes to the page and clicks Save (which is enabled)
      7. User B gets the message "You are not permitted to perform this operation"

      Other Steps to replicate

      1. Make User A as the member of confluence-administrators group
      2. User A creates a space and makes User B the only Space Administrator
      3. User A goes to the page and the edit function is enabled
      4. User A Clicks Edit and starts to make changes
      5. User A finishes making changes to the page and clicks Save (which is enabled)
      6. User A gets the message "You are not permitted to perform this operation"
      7. User A gets blank page below main Confluence top navigation bar when clicking Close after entering editor.

      Workarounds

      There are a few workarounds to this, and reasons why we don't see this bug as critical:

      1. Most importantly, Atlassian recommends not using your administration account for regular use of Confluence. Create separate admin and user accounts instead.
      2. Use your admin powers to grant yourself permission to edit the page (at space and page level as required), then edit the page again.
      3. Use the back button to get back to your changes and copy/paste them for saving as a user that is explicitly permitted to edit the page. (If the back button doesn't work in your scenario, please raise a ticket with steps to reproduce - we'd like to fix this.)
      4. Until CONF-4616 is fixed, grant administrators "System Administration" permission but do not put them in the "confluence-administrators" group if you do not wish them to have access to all content in your system. (This is in relation to the original bug.)

            [CONFSERVER-25210] "Not Permitted" page when members of confluence-administrators attempt to edit pages on which they do not have edit permission

            sarat added a comment -

            In 6.0.2  I encountered this problem as well, its strange issue as I admin you should be able to edit any space. So its bug from confluence side.

            sarat added a comment - In 6.0.2  I encountered this problem as well, its strange issue as I admin you should be able to edit any space. So its bug from confluence side.

            In 5.9.7 I encountered this problem as well, mainly on the spaces I did not create. For me the workaround was not to create a new user account, but to just add specific user-access rights on these spaces for my (admin) account. 

            patrick-rely added a comment - In 5.9.7 I encountered this problem as well, mainly on the spaces I did not create. For me the workaround was not to create a new user account, but to just add specific user-access rights on these spaces for my (admin) account. 

            Also have the issue in 5.10.
            As admin I can edit and save the page. Only when I first add a reaction or inline comment I get the no permission when trying to edit the page.
            When editing the page and closing it without saving, I get the blank page. Pressing the back button of the browser gives the no permission message.

            Patrick Vanhoof added a comment - Also have the issue in 5.10. As admin I can edit and save the page. Only when I first add a reaction or inline comment I get the no permission when trying to edit the page. When editing the page and closing it without saving, I get the blank page. Pressing the back button of the browser gives the no permission message.

            Matt Ryall added a comment -

            I can see how this is occasionally frustrating, but I don't see how this can be a "huge inconvenience". This bug only prevents those with the highest level of admin access in Confluence from editing pages they technically don't have permission to edit, due to either space permissions or page restrictions.

            In addition to the other workarounds listed, another easy workaround is to use your admin powers to grant yourself permission first, then you can edit without hitting this issue. I'll add this to the list in the description.

            This bug is still open because we would definitely like to fix it. But it is in the queue behind other more impactful bugs right now.

            Matt Ryall added a comment - I can see how this is occasionally frustrating, but I don't see how this can be a "huge inconvenience". This bug only prevents those with the highest level of admin access in Confluence from editing pages they technically don't have permission to edit, due to either space permissions or page restrictions. In addition to the other workarounds listed, another easy workaround is to use your admin powers to grant yourself permission first, then you can edit without hitting this issue. I'll add this to the list in the description. This bug is still open because we would definitely like to fix it. But it is in the queue behind other more impactful bugs right now.

            We recently upgraded to Confluence 5.9.10 and are also encountering this issue.

            Joe Francisco added a comment - We recently upgraded to Confluence 5.9.10 and are also encountering this issue.

            @Matt Ryall- if I understand you correctly, admins should have to use 2 Confluence license seats? One for admin purposes and one for general use? That makes no sense whatsoever. This is a major bug for us not to mention a huge inconvenience for the licensing price we pay. I'm working on admin tasks for most of my day. Does that mean I have to toggle in and out of user accounts while I work in Confluence as well as admin Confluence? Ridiculous!

            Sofia Castaneda added a comment - @Matt Ryall- if I understand you correctly, admins should have to use 2 Confluence license seats? One for admin purposes and one for general use? That makes no sense whatsoever. This is a major bug for us not to mention a huge inconvenience for the licensing price we pay. I'm working on admin tasks for most of my day. Does that mean I have to toggle in and out of user accounts while I work in Confluence as well as admin Confluence? Ridiculous!

            I agree that this may not be the highest priority issue because people generally shouldn't be using an admin account for regular work. However, I often have to log in using the admin account to diagnose Confluence problems, and then I forget that I'm logged in as that user. When I then start trying to do regular work (i.e. editing a page), I get a nasty surprise when I try to save the page.

            So another way to resolve this may be to make it more obvious to a user if they are logged in using an admin account - perhaps by changing colours in a prominent location.

            Note that this issue is not limited to pages with restrictions, but also affects unrestricted pages in spaces in which the admin account does not have edit permissions (at the space level).

            Luckily I can usually "recover" the lost work by editing the page again, viewing the changes in the draft, logging back in as the normal user, and then manually re-applying the changes. But it's just really frustrating when it happens.

            Gareth White added a comment - I agree that this may not be the highest priority issue because people generally shouldn't be using an admin account for regular work. However, I often have to log in using the admin account to diagnose Confluence problems, and then I forget that I'm logged in as that user. When I then start trying to do regular work (i.e. editing a page), I get a nasty surprise when I try to save the page. So another way to resolve this may be to make it more obvious to a user if they are logged in using an admin account - perhaps by changing colours in a prominent location. Note that this issue is not limited to pages with restrictions, but also affects unrestricted pages in spaces in which the admin account does not have edit permissions (at the space level). Luckily I can usually "recover" the lost work by editing the page again, viewing the changes in the draft, logging back in as the normal user, and then manually re-applying the changes. But it's just really frustrating when it happens.

            Also, if you don't have permission do edit and click on Close instead of Save, the page gets blank. It doesn't refresh it or it doesn't redirect you back again to the "view" mode.

            Guilherme V. (Inactive) added a comment - Also, if you don't have permission do edit and click on Close instead of Save , the page gets blank. It doesn't refresh it or it doesn't redirect you back again to the "view" mode.

            Same issue over here

            The suggested workaround does not work on our site. I removed the membership of confluence-administrators for 'user123' and granted him individual site admin permissions. When this 'user123' now tries to access a space he already gets the not permitted error.

            Jens Kasperek (Bosch GmbH) (Inactive) added a comment - - edited Same issue over here The suggested workaround does not work on our site. I removed the membership of confluence-administrators for 'user123' and granted him individual site admin permissions. When this 'user123' now tries to access a space he already gets the not permitted error.

            This is not a minor bug for us.
            We use Digital Certificates for single-sign-on, so there is no way for users to have dual accounts, one for "normal" and one for "System Admin" work.

            Peter Binney added a comment - This is not a minor bug for us. We use Digital Certificates for single-sign-on, so there is no way for users to have dual accounts, one for "normal" and one for "System Admin" work.

              qpham@atlassian.com Quan Pham
              acampbell AndrewA
              Affected customers:
              34 This affects my team
              Watchers:
              53 Start watching this issue

                Created:
                Updated:
                Resolved: