You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org> on 2010/02/15 12:45:28 UTC

[jira] Reopened: (CLEREZZA-107) Usermanager: method to return user as resource

     [ https://issues.apache.org/jira/browse/CLEREZZA-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reto Bachmann-Gmür reopened CLEREZZA-107:
-----------------------------------------


merged down ZZ-107 but now there's a permission issue when accessing e.g. the Dashboard

> Usermanager: method to return user as resource
> ----------------------------------------------
>
>                 Key: CLEREZZA-107
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-107
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Reto Bachmann-Gmür
>            Assignee: Manuel Innerhofer
>
> UserManager.getUserByName(name): deprecate or remove this method, if one has access to the system gaph getting the resource is trivial to get this resource, otherwiese it might be used wrongly as this is done in HierachyManager.
> getUserGraphNode(name): it's off little use to have the GraphNode with in "UnionMGraph between a new SimpleMGraph and the system graph". I suggest to have
> getUserInSystemGraph(name) : GraphNode -> The user in the system graph
> getUserGraphNode(name) : GraphNode -> Returns the current user in an Editable MGraph (i.e. a SimpleGraph but this is implementation specific) with the context of the user node, editing the graphnode('s Mgaph) doesn't cause any change elsewhere.
> I'm not sure if we should also include information contained in the content graph, I tend to think taht this should be done elsewhere if needed

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.