You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Marcus Christie (JIRA)" <ji...@apache.org> on 2018/10/02 21:44:00 UTC

[jira] [Updated] (AIRAVATA-2893) Add Keycloak password to sharing catalog when new gateway is created

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

Marcus Christie updated AIRAVATA-2893:
--------------------------------------
    Issue Type: Bug  (was: Improvement)

> Add Keycloak password to sharing catalog when new gateway is created
> --------------------------------------------------------------------
>
>                 Key: AIRAVATA-2893
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2893
>             Project: Airavata
>          Issue Type: Bug
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Minor
>
> When a new gateway is created a password credential is generated for the admin username and password. When it is created the gateway isn't yet replicated to the sharing catalog so there isn't a way to register an Entity for this credential at that time, so I'm not exactly sure when is best to register it with the sharing catalog.
> Marking this as lower priority since there really isn't much we can do with this credential even if it were registered in the sharing catalog. The only "problem" is that, with the group based auth applied to credentials, admins won't see this credential listed under password credentials in the portal and it won't be returned by any of the API server methods.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)