-
Bug
-
Resolution: Low Engagement
-
Medium
-
None
-
5.4.1
-
Operating System Windows Server 2008 R2 6.1
OS Architecture amd64
Application Server Apache Tomcat/6.0.35
Servlet Version 2.5
Java Version 1.7.0_15
-
2
-
Severity 2 - Major
-
0
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
To reproduce, create a space "TestBug" in Confluence, then do the following on the space permissions:
- Strip out all Anonymous access from TestBug
- Remove the jira-administrators group from group permissions (note we are using integrated access from JIRA)
- Add in admin-user1 to the individual users section
- Login as admin-user2
- Confirm that admin-user2 is unable to see TestBug space in list of spaces
- Go to Confluence Admin -> Space Permissions
- Press the "Recover Permissions" button for TestBug
- It should change to "Manage Permissions"; try to click that link
- You should get to an error page saying Not Permitted
Now, back as admin-user1, you can validate that admin-user2 got added to the individual users section as an Admin, but has no View access, so cannot see the admin page.
This is bad news if you dont have a fellow admin to help you unlock yourself or regain access.
- is cloned from
-
CONFSERVER-33411 "Recover Permissions" does not work on a site if jira-administrators group not set
-
- Closed
-
- is duplicated by
-
CONFSERVER-35201 Recover Space Permissions feature in Confluence is broken
-
- Closed
-
-
CLOUD-7363 Permissions changes not reflecting
- Closed
- relates to
-
CONFCLOUD-34213 Recover Permissions - does not work on a site if jira-administrators group not set
-
- Closed
-
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center