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 Wed, 02 Nov 2016 19:25:58 GMT

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

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

[~eroma_a],

This problem where sharing an experiment shares the project was the result of an older workaround
implemented in PGA where the project of the experiment is also shared with the user.  I discussed
with Supun and it should be safe to remove now.

However, with that done, I've now run into a problem on the experiment summary page where
I can't display the name of the project of the experiment when the user doesn't have read
access to the project.  What do you think is ideal to happen in this scenario?  I can think
of a couple implementation options
* just don't show the name of the project
* instead of the project name, display _You currently don't have access to this project_ or
some similar message


> 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