[
https://issues.apache.org/jira/browse/AIRAVATA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702425#comment-13702425
]
Saminda Wijeratne commented on AIRAVATA-880:
--------------------------------------------
That is correct. Right now we assume the user is admin and they can do
everything (authoring descriptors/workflows/experiments). But as I understand
you are not trying to retrieve a list of users who has "admin rights" right?
Just all the users or the users who can run experiments?
Could you breifly define the portal users who can access your dashboard and
what users a portal user can querie to get data in the current design? And if
you have any future directions to the design that would also be helpful if
anyone wants to do follow up developement of your work.
> Have a UserRegistry API to support user related operations
> ----------------------------------------------------------
>
> Key: AIRAVATA-880
> URL: https://issues.apache.org/jira/browse/AIRAVATA-880
> Project: Airavata
> Issue Type: Improvement
> Components: Registry API
> Affects Versions: 0.9
> Reporter: Viknes Balasubramanee
> Attachments: Airavata-880.patch
>
>
> Implement an API to deal with User Management related operations. This would
> be useful for the webapps that are going to be developed as a part of the
> GSOC projects and also to support monitoring capabilities(preferably by
> admins) by these webapps
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
