[MAGNOLIA-1786] Review user api, use it in trees, ... Created: 17/Oct/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.5 RC1
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Sameer Charles
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1709 Users, Groups and Roles trees should ... Closed
supersession
supersedes MAGNOLIA-1330 Expose arbitrary properties for User ... Closed
supersedes MAGNOLIA-1735 Ability to change a user's password t... Closed
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:

 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)


 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:30:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.