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] [Assigned] (AIRAVATA-2817) Admins need READ and WRITE permission, not just WRITE
Date Thu, 07 Jun 2018 15:01:00 GMT

     [ https://issues.apache.org/jira/browse/AIRAVATA-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcus Christie reassigned AIRAVATA-2817:
-----------------------------------------

       Assignee: Marcus Christie
    Description: 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.
     Issue Type: Bug  (was: Story)

> 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)

Mime
View raw message