[
https://issues.apache.org/jira/browse/AIRAVATA-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504794#comment-16504794
]
ASF subversion and git services commented on AIRAVATA-2817:
-----------------------------------------------------------
Commit f91e93c454d3b3ec69577773295ab10c1fb2dfb3 in airavata's branch
refs/heads/group-based-auth from [~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=f91e93c ]
AIRAVATA-2817 AIRAVATA-2781 Give Admins READ as well as WRITE
Also removing sharing Projects with Admins groups.
> Admins need READ and WRITE permission, not just WRITE
> -----------------------------------------------------
>
> Key: AIRAVATA-2817
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2817
> Project: Airavata
> Issue Type: Bug
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> The migration script gives the "Admins" group WRITE permission but they also
> explicitly need READ permission. I was thinking that the READ permission
> would be implicit but how we've implemented it so far is to grant READ
> directly instead of inferring it when a user has WRITE permission.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
