[MAGNOLIA-7903] Impact of using jcrName on MgnlUserManager Created: 15/Oct/20 Updated: 11/Dec/20 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 6.2.3 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
While attempting to create a new user in the Security app I stumbled upon something strange. Reproduce
We should think about how this is going to work since the current MgnlUserManager depends on the actual name of the node and not the jcrName. The person creating the user can only control the jcrName. Therefore duplicating leaves you in a weird scenario. |