[ http://jira.magnolia.info/browse/MAGNOLIA-1786?page=all ]
Grégory Joseph updated MAGNOLIA-1786:
-------------------------------------
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)
was:
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)
> Review user api, use it in trees, ...
> -------------------------------------
>
> Key: MAGNOLIA-1786
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1786
> Project: Magnolia
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.1
> Reporter: Grégory Joseph
> Assigned To: Sameer Charles
> Fix For: 3.2
>
>
> 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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
