airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2431) Create the Keycloak realm as part of migration
Date Tue, 06 Jun 2017 17:52:18 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039339#comment-16039339
] 

Marcus Christie commented on AIRAVATA-2431:
-------------------------------------------

Just realized we should also migrate the gateway to the Profile Service too.  That's kind
of separate from user migration, but since the Profile Service is new and unpopulated might
as well create the gateway profiles at this time.

> Create the Keycloak realm as part of migration
> ----------------------------------------------
>
>                 Key: AIRAVATA-2431
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2431
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Security
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>             Fix For: 0.18
>
>
> Currently the MigrationManager assumes that there already is a Keycloak realm in which
to migrate users.  This requires that someone manually create a Keycloak realm, which would
be error prone and time consuming for migrating all of the gateways we want to migrate.
> Instead, the MigrationManager should create the Keycloak realm as part of the migration.
 We already have [Keycloak realm creation/setup service method in the Profile Service|https://github.com/apache/airavata/blob/58ea1bfe780d7aaf34cabf886ca298d5e9b1c8ee/thrift-interface-descriptions/service-cpis/profile-service/iam-admin-services/iam-admin-services-cpi.thrift#L46-L46].
We should make use of that.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message