airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-2431) Create the Keycloak realm as part of migration
Date Tue, 06 Jun 2017 17:47:18 GMT


ASF subversion and git services commented on AIRAVATA-2431:

Commit c26f289595ffca771d93e2014f7572f3a6e01ebc in airavata's branch refs/heads/develop from
[;h=c26f289 ]

AIRAVATA-2431 Allow duplicate emails in Keycloak realm

Also bug fix: closing HTTP Response to free up connections (otherwise
running the migration hangs after about 10 users, which is probably
because the 10 connections in the Resteasy connection pool are all in

> Create the Keycloak realm as part of migration
> ----------------------------------------------
>                 Key: AIRAVATA-2431
>                 URL:
>             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|].
We should make use of that.

This message was sent by Atlassian JIRA

View raw message