[
https://issues.apache.org/jira/browse/AIRAVATA-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764659#comment-15764659
]
ASF GitHub Bot commented on AIRAVATA-2232:
------------------------------------------
GitHub user machristie opened a pull request:
https://github.com/apache/airavata/pull/92
AIRAVATA-2232 Filter by CredentialOwnerType
Filtering by CredentialOwnerType in new SummaryType methods.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/machristie/airavata
AIRAVATA-2232-gateway-creds-in-user-settings
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/airavata/pull/92.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #92
----
commit b22499c02d9f9fdbb452492f8c80a266a40cb464
Author: Marcus Christie <[email protected]>
Date: 2016-12-20T16:53:38Z
AIRAVATA-2232 Filter by CredentialOwnerType
Filtering by CredentialOwnerType in new SummaryType methods.
----
> 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)
