Details
-
Improvement
-
Resolution: Won't Do
-
Major
-
None
-
3.5 RC1
-
None
Description
To be determined / discussed:
- Maybe we want/need to be able to apply operations on a user/group/role with a single save. (ie operations like setProperty should not save the user's node as they do at the moment)
- For consistency's sake, we may also want to make the trees use the appropriate User/Group/RoleManager instead of applying the operations on the nodes directly.
- How to handle the relationship between a User/Group/RoleManager and it's tree in the ui ? At the moment, it might be confusing for users using ldap or another external user management, to have a tree for users, groups or roles, that basically does nothing and does not reflect the state of their system. ("wrong" list of users, etc)
- Do we want more complex/typed properties for users/groups? (simple Strings at the moment)
Checklists
Acceptance criteria
Attachments
Issue Links
- is related to
-
MAGNOLIA-1709 Users, Groups and Roles trees should use their respective Managers
-
- Closed
-
- supersedes
-
MAGNOLIA-1330 Expose arbitrary properties for User and Group
-
- Closed
-
-
MAGNOLIA-1735 Ability to change a user's password through the API
-
- Closed
-