[
https://issues.apache.org/jira/browse/AIRAVATA-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706364#comment-15706364
]
Marcus Christie commented on AIRAVATA-2232:
-------------------------------------------
Ran the following on dev_credentialstore_gw56:
{code:sql}
alter table CREDENTIALS add column CREDENTIAL_OWNER_TYPE VARCHAR(10) DEFAULT
'GATEWAY' NOT NULL;
update
dev_credentialstore_gw56.CREDENTIALS
set
credential_owner_type = 'USER'
where
token_id in (
select
resource_cs_token
from
dev_appcatalog_gw56.USER_COMPUTE_RESOURCE_PREFERENCE
union
select
RESOURCE_CS_TOKEN
from
dev_appcatalog_gw56.USER_STORAGE_PREFERENCE
UNION
select
cs_token
from
dev_appcatalog_gw56.USER_RESOURCE_PROFILE
);
{code}
> 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)
