[MAGNOLIA-8420] Replace groups by role nesting Created: 19/May/22 Updated: 05/Sep/22 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Evzen Fochr | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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)
|
| Date of First Response: | |
| Epic Link: | Security maintenance |
| Team: |
| Description |
|
Actual state of security is combination of Role based (path restrictions in security app) and Rule based (availability rules for apps and actions) access control. Role can’t be in parent relation for another role. We have groups that are not native in Role Based Access Control and serves for creating tree structure. AC: |
| Comments |
| Comment by Matt Rajkovic [ 05/Sep/22 ] |
|
Will need to be reviewed if still needed. |