-
Type:
Bug
-
Resolution: Low Engagement
-
Priority:
Low
-
None
-
Affects Version/s: 6.13.0, 7.0.2
-
Component/s: Content - Restrictions
-
1
-
Severity 3 - Minor
Issue Summary
Suppose a user send a request access to a certain page. Approving the request revokes access privileges of all others except the requester. This happens if the page is affected by CONFSERVER-32712 .
Two underlying problems
- Requesting access to a restricted page is enabled even though it only has inherited restriction.
- Approving the request revokes other's privilege to view the page
Environment
Confirmed in Confluence 7.0.2 but would be replicated in the newer version as well.
Steps to Reproduce
- Add SMTP server for Confluence
- Login as admin, an administrator user
- Add user1 and user2
- Remove them from confluence-users
- Grant "Use Confluence" permission individually to them
- Create pages with such tree structure
RootPage ├── pageA └── pageB - In space permission,
- Restrict view access for RootPage only to user1, user2
- Restrict view access for PageB only to user1
- Add page C below page B
RootPage ├── pageA └── pageB └── pageC - Move page C to below page A
RootPage ├── pageA └── pageC └── pageB - Login to user2 and visit pageC
Expected Results
user2 can see pageC.
Otherwise user2 cannot send request access even the page is affected by CONFSERVER-32712 .
Actual Results
- user2 cannot see pageC and the access request screen is enabled. Request can be sent as
- Approving request will make PageC be only visible to user2
Notes
The potential problem of this issue is CONFSERVER-32712, so resolving the bug will also resolve this.
Workaround
Don't send access request to any page that is affected by CONFSERVER-32712
- derived from
-
CONFSERVER-32712 Inherited page restrictions not updated when page is moved
-
- Gathering Impact
-