[
https://issues.apache.org/jira/browse/AIRAVATA-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702475#comment-13702475
]
Viknes Balasubramanee commented on AIRAVATA-880:
------------------------------------------------
Gateway admins will be the users of my portal. Admins should be able to see
other admin users in the system and also see all the users of the system who
can run workflows/experiments. The admins should be able to query for
experiments by particular user, date, id or execution status. Modifying
experiment/workflow data and user management is not a part of my requirement. I
will not be adding any POST/PUT/DELETE operations as of now. I might work on
adding the methods mentioned above by Amila if i get extra time. This would
require POST operations and we should come up with an authorization mechanism
for that.
My suggestion is we add a column to the DB specifying the type(admin or
experiment runner) of user. Then after authentication, when the user tries to
hit a particular URL, we intercept it through a filter and based on the user
type and his rights, we allow him to access the URL and do the required
operations. I have worked with such filters in Spring Security but i am not
sure if we have something similar with Jersey Endpoints. Whoever is going to
work on it will have to evaluate it and proceed further.
> 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
