airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eroma (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (AIRAVATA-2232) All SSH keys generated by a gateway admin are listed in user's settings --> credential store
Date Mon, 19 Dec 2016 20:37:58 GMT

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

Eroma reopened AIRAVATA-2232:
-----------------------------

Still issues exits in https://dev.seagrid.org
Even with the CREDENTIAL_OWNER_TYPE
DEVEroma2017 created a new gateway credential and it appeared in User settings. I was also
able to delete it from user settings and it also got removed from the gateway credentials
as it was the same key

> All SSH keys generated by a gateway admin are listed in user's settings --> credential
store
> --------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2232
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2232
>             Project: Airavata
>          Issue Type: Bug
>          Components: Airavata System, PGA PHP Web Gateway
>         Environment: dev.seagrid.org
>            Reporter: Eroma
>            Assignee: Eroma
>
> Gateway admins generates SSH keys for the gateway, to be used in community account usage.
Also admins will generate SSH keys to be used with their own user settings for compute resources.
> All these keys are listed under users own credential store. Users own crendetial store
should only have keys generated for own resource logins. This is through User settings in
PGA.



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

Mime
View raw message