-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2
-
Fix Version/s: 6.1.2 CE GA3, 6.1.30 EE GA3, 6.2.0 CE M5
-
Component/s: User Management, User Management > Roles
-
Labels:
-
Environment:Tomcat 7.0.25 + MySQL 5. 6.1.x GIT ID: 4f4faddc8768053bb86a3a593e73845179886795.
Tomcat 7.0.27 + MySQL 5. Portal 6.1.x EE GIT ID: 0194e5337a7371291163a76a24d98f2417adaa27.
-
Branch Version/s:6.1.x
-
Backported to Branch:Committed
-
Fix Priority:3
-
Git Pull Request:
According to the help blurb for Clean Up Permissions (see CleanUpPermissionsHelp.jpg), the help blurb gives the impression that this should remove the Add to Page permission entirely from the Guest and User and reduce the scope of the Add to Page permission to user personal site for the Power User role.
After executing clean up permissions the first time, the "Add to Page" portlet permissions for the User role are reduced in scope to the user personal site. If execute clean up permissions is run a second time, those Add to Page permissions will be removed from the User role entirely.
Steps to reproduce:
- Navigate to Control Panel > Roles
- For the User role, click Actions > Define Permissions. Notice that the Add to Page permissions for all the portlets are present. (See BeforeCleanUpPermissions.jpg)
- Navigate to Control Panel > Server Administration
- Click Execute next to Clean Up Permissions
- Navigate back to Control Panel > Roles
- For the User role, click Actions > Define Permissions. Notice that the Add to Page permissions have been reduced in scope to User Personal Site. (See AfterCleanUpPermissions1.jpg)
- Navigate to Control Panel > Server Administration
- Click Execute next to Clean Up Permissions
- Navigate back to Control Panel > Roles
- For the User role, click Actions > Define Permissions. Notice that this time, the Add to Page permissions have been removed entirely. (See AfterCleanUpPermissions2.jpg)
