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 2017/06/08 16:35:18 UTC
[jira] [Resolved] (AIRAVATA-2431) Create the Keycloak realm as part
of migration
[ https://issues.apache.org/jira/browse/AIRAVATA-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Christie resolved AIRAVATA-2431.
---------------------------------------
Resolution: Fixed
Only code change not tested is that I added the Keycloak admin user to the "admin" role when it is created. I'll test that when I test migrating the scigap gateway.
> 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)