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/05/25 14:27:04 UTC

[jira] [Updated] (AIRAVATA-2402) Keycloak user migration: migrate user roles

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

Marcus Christie updated AIRAVATA-2402:
--------------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: AIRAVATA-2406

> Keycloak user migration: migrate user roles
> -------------------------------------------
>
>                 Key: AIRAVATA-2402
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2402
>             Project: Airavata
>          Issue Type: Sub-task
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>             Fix For: 0.18
>
>
> MigrationManager should migrate user roles from IS to Keycloak.
> The migration should also be able to map roles from whatever they are defined as in IS to the static role names we're using for Keycloak:
> * admin
> * admin-read-only
> * gateway-user
> * user-pending
> * gateway-provider
> So for example Ultrascan's user role name is {{airavata-user}} in WSO2 IS but during the migration we want to map this to {{gateway-user}} in Keycloak.



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