[jira] [Commented] (AIRAVATA-1624) [GSoC] Securing Airavata API

["Suresh Marru (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRAVATA-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350920#comment-14350920 ] 

Suresh Marru commented on AIRAVATA-1624:
----------------------------------------

Hi Hasini,

Please refer to [1] for some brief discussion on this topic. In Scenario 2 of your document (figure 3) does wso2IS currently have such user store extension or will it have to be written? What will be the requirement of Gateway User Store? I am assuming most of these include a custom mysql user management or some use bundled postgre database like with drupal/wordpress. 

Suresh
[1] - http://markmail.org/thread/vveb33oefxdbecxq

> [GSoC] Securing Airavata API
> ----------------------------
>
>                 Key: AIRAVATA-1624
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1624
>             Project: Airavata
>          Issue Type: New Feature
>          Components: Airavata API
>            Reporter: Suresh Marru
>              Labels: gsoc, gsoc2015, mentor
>         Attachments: Securing_ARAVATA_API_V1.pdf
>
>
> Apache Airavata uses Thrift based API's for external facing API's and for system internal CPI's. The API's need to be secured adding authentication and authorization capabilities. 
> The Authentication need to ensure only approved users/clients can communicate. Similarly clients should only interact with valid servers. 
> Authorization need to be enforced to ensure only users with specific roles can appropriately access specific API's. As an example, administrative roles should be able see all the users experiments where as end users can only see his/her data and not access other information (unless explicitly shared). 
> Earlier GSoC project focused on this topic has relavent discussion. 
> https://cwiki.apache.org/confluence/display/AIRAVATA/GSoC+2014+-+Add+Security+capabilities+to+Airavata+Thrift+services+and+clients



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)