You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Marcus Christie (JIRA)" <ji...@apache.org> on 2018/06/08 14:52:00 UTC
[jira] [Reopened] (AIRAVATA-2817) Admins need READ and WRITE
permission, not just WRITE
[ https://issues.apache.org/jira/browse/AIRAVATA-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Christie reopened AIRAVATA-2817:
---------------------------------------
> 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)