airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2190) User A shared a single experiment with User B, read access. Project is also shared now with User B.
Date Thu, 03 Nov 2016 15:38:59 GMT

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

Marcus Christie commented on AIRAVATA-2190:
-------------------------------------------

I'm looking into what it would take to clone an experiment into a different project. This
ability is needed when a user has read access to a shared experiment but no write access to
the project it is in.

The Airavata API method {{cloneExperiment}} clones an experiment in the same project. This
API method would need to be updated in order to allow cloning an experiment into a different
project.

I think I can make the changes to the cloneExperiment method to allow passing in also the
projectId under which to create the cloned experiment so I'll give that a shot.

> User A shared a single experiment with User B, read access. Project is also shared now
with User B.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2190
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2190
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway
>         Environment: https://dev.seagrid.org
>            Reporter: Eroma
>            Assignee: Marcus Christie
>             Fix For: 0.17-SNAPSHOT
>
>
> Steps
> 1. User A shared a single experiment with user B. With read access
> 2. User B now has access to User A's project which experiment belongs
> 3. User B can create new experiments under the Project.
> 4. User B can cancel the shared experiment irrespective of having only read access
> 5. user B can clone the shared experiment and create a new experiment under the same
project and remove sharing of the project owner. 
> 6. Original user A cannot see the cloned experiment under his own project
> User B should not be able to create any experiments under the project the shared experiment
belongs. 
> No should be able to cancel the shared experiment, only has read access.
> If cloned should create it under own project; not with user A's project



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

Mime
View raw message