[SECURITY-71] Consider backwards compatibility with ACLs defined in JCR roles and users Created: 27/Oct/23 Updated: 29/Nov/23 |
|
| Status: | Open |
| Project: | Security |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | parked | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Epic Link: | Sane Default Roles & Groups | ||||
| Description |
|
As 6.3 aims to support permissions/ACLs via MP config, consider backwards compatibility needs:
Additional note: even if customers don't strictly need to update, the old ways will be perceived as legacy/deprecated, so they generally want to stay up-to-date, so let's facilitate porting, minimize the overhead, auto-conversion possibilities, etc. |