[
https://issues.apache.org/jira/browse/AIRAVATA-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690658#comment-15690658
]
Marcus Christie commented on AIRAVATA-2232:
-------------------------------------------
I'm not sure if we want to add this CredentialOwnerType as an attribute of all
credentials instead of just SSHCredential. I can't see a use case for a user
PasswordCredential.
But to support querying I would want to put the CredentialOwnerType as a column
on the CREDENTIALS table. However, that would seem like a data model mismatch
if there is a column that applies to only SSHCredentials, but not the others.
Maybe there should be a table for SSH_CREDENTIALS that has (gateway_id,
token_id, credential_owner_type) columns.
> 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: Marcus Christie
>
> 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)
