airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-1783) Additional Role to have read-only dashboard access
Date Sat, 18 Jul 2015 14:23:05 GMT

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

ASF subversion and git services commented on AIRAVATA-1783:
-----------------------------------------------------------

Commit 6ea67871ce53df3a7f6fc88b085c12cca7fa7cf4 in airavata-php-gateway's branch refs/heads/0.15-release-branch
from [~scnakandala]
[ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=6ea6787 ]

implementing AIRAVATA-1783


> Additional Role to have read-only dashboard access
> --------------------------------------------------
>
>                 Key: AIRAVATA-1783
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1783
>             Project: Airavata
>          Issue Type: New Feature
>          Components: PGA PHP Web Gateway
>            Reporter: Suresh Marru
>            Assignee: Supun Chathuranga Nakandala
>
> A dry-run of the tutorial shows all participants appreciated the dashboard functionality
and  wanted to play around. Giving admin access is risky as then can potentially change app
catalog entries. 
> Can we add an additional role -'admin-read-only' and also handle this in admin dashboard
so they can have only the view buttons but not create/update. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message