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

Eroma commented on AIRAVATA-2191:
---------------------------------

Current scenario (Tested in https://beta.seagrid.org):
1. User A creates a project and shares with user B with read access
2. User A creates an experiment and removes user B from the experiment sharing.
3. In Create experiment it shows as if the sharing was removed from user B but 
when the experiment is saved and launched it is displayed as its still shared 
with user B. So the sharing was not actually removed because the sharing is at 
project level with user B.
4.  A new experiment is shared at experiment level with user C and remove user B
5. Since user B cannot be removed experiment is shared with both users at the 
end


> Experiment of User A got automatically shared with User B when User A shares 
> another experiment with user C
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2191
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2191
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway
>         Environment: https://dev.seagrid.org
>            Reporter: Eroma
>            Assignee: Marcus Christie
>             Fix For: 0.17
>
>         Attachments: Screen Shot 2016-10-25 at 12.02.53 PM.png
>
>
> 1. User A create Project A and shares it with User B
> 2. User A creates an experiment under Project A but removes sharing with User 
> B
> 3. User A creates another experiment and shares it with User C under the same 
> project A
> 4. Upon sharing second experiment with User C, the first one now appears as a 
> shared experiment for User B. Even when it is not shared.
> 5. When User B tries to view the experiment summary throws the attached 
> exception.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to