Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Date: Sun, 8 Mar 2015 00:46:38 +0000 (UTC)
From: "Hasini Gunasinghe (JIRA)" <jira@apache.org>
To: dev@airavata.apache.org
Message-ID: <JIRA.12780155.1425671042000.30592.1425775598526@Atlassian.JIRA>
In-Reply-To: <JIRA.12780155.1425671042000@Atlassian.JIRA>
References: <JIRA.12780155.1425671042000@Atlassian.JIRA>
 <JIRA.12780155.1425671042314@arcas>
Subject: [jira] [Commented] (AIRAVATA-1624) [GSoC] Securing Airavata API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hasini Gunasinghe commented on AIRAVATA-1624:
---------------------------------------------

Hi Suresh,

Thank you for the encouraging reply. Sure, I will create the GSoC application both in google melange system as well as in the AIRAVATA wiki. 
Please let me know if you get any further questions/comments on the proposed solution.

Thanks & Best Regards,
Hasini.


> [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)