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

Marcus Christie commented on AIRAVATA-2191:
-------------------------------------------

Regarding Eroma's suggestion
{quote}
In that case, we should not let the user remove the sharing at experiment 
level. We should give a message and ask that he stop project level sharing.
{quote}

I would prefer if we updated the sharing APIs to help with and enforce this.  I 
think from PGA side I need the following from the API
* currently getAllAccessibleUsers just returns who can READ or WRITE, etc.  
However, PGA needs to know which of those permissions can be removed for that 
resource. For example, if a user can READ an experiment because the user has 
been given READ permission to the project, then for the experiment resource the 
user has a READ permission that cannot be revoked for the experiment.
* revokeSharingOfResourceFromUsers should throw an error in the scenario above. 
It shouldn't allow removing a user's access to an experiment that was granted 
at the project level.


> 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.4#6332)

Reply via email to