[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

  • Duplicate the user eric
  • Notice two things:
    • You can save another user with the same jcrName (should this be restricted?)
    • I cannot rename the node I just duplicated which means that I cannot control the username. If I duplicate I am stuck with the automated name that was create for me, eric0.

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.


Generated at Mon Feb 12 04:27:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.