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 2017/07/28 14:40:00 UTC
[jira] [Updated] (AIRAVATA-2459) Remove gateway-user and
admin-read-only roles from ScigaP portal
[ https://issues.apache.org/jira/browse/AIRAVATA-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eroma updated AIRAVATA-2459:
----------------------------
Fix Version/s: (was: 0.18)
0.19
> Remove gateway-user and admin-read-only roles from ScigaP portal
> ----------------------------------------------------------------
>
> Key: AIRAVATA-2459
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2459
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Affects Versions: 0.17
> Environment: https://dev.scigap.org/
> Reporter: Eroma
> Assignee: Marcus Christie
> Fix For: 0.19
>
>
> Roles should exists in super admin portal similar to production. gateway-user and admin-read-only doesn't make sense in super admin portal
> *In current production *
> 1. Super admin portal only has gateway-provider, admin and user-pending
> 2. When new users creates account by default they get gateway-provider and admin
> 3. If scigap admins want to block this user needs to explciitly give user-pending
> 4. When user-pending role given, both gateway-provider and admin gets removed.
> 5. When gateway-provider is given back user will have both gateway-provider and user-pending
> 6. When given admin to same user, user-pending is replaced by admin
> 7. Assumption: New users are to request gateways, so they are not required to be given a active role after inquiring.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)