[MGNLUI-3886] Exclude workspaces in the JCR Browser app, based on the user's group Created: 23/May/16 Updated: 25/Oct/18 Resolved: 25/Oct/18 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
The goal of this ticket is to be able to allow for a fine tuning of group-workspaces permissions in the JCR Browser app. This would for instance allow to hide the config workspace to users who are not part of the superuser group. Here is a proposal to solve this problem. First, create the following JCR hierarchy under /modules/jcr-browser-app/apps/jcr-browser/subApps/browser/contentConnector/excludes:
Secondly, in JcrBrowserContextTool#populateWorkspaceNames: 1. get the current user's groups |
| Comments |
| Comment by Roman Kovařík [ 23/May/16 ] |
|
Isn't listing only these workspaces where the user has write permissions enough? Instead of an additional configuration? |