You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2015/07/20 19:03:04 UTC
[jira] [Closed] (AIRAVATA-1783) Additional Role to have read-only
dashboard access
[ https://issues.apache.org/jira/browse/AIRAVATA-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eroma closed AIRAVATA-1783.
---------------------------
tested and verified in
http://test-drive.airavata.org/pga/public
> 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)