airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2342) Integrate Keycloak with PGA
Date Sat, 25 Mar 2017 17:37:42 GMT

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

ASF subversion and git services commented on AIRAVATA-2342:
-----------------------------------------------------------

Commit f065beeb7f84db9347fe3afdd7d0cac84b5f9e15 in airavata-php-gateway's branch refs/heads/keycloak-integration
from [~marcuschristie]
[ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=f065bee ]

AIRAVATA-2342 Reverting to using username in API

One difference between the Keycloak API and the WSO2 IS API is that
where WSO2 IS expects the username, Keycloak expects the Keycloak user
id.  This made for a mismatch in how to call the facade for WSO2 IS and
Keycloak.  However, now that I have a way to get the user id from the
username, I was able to revert some changes earlier so that now WSO2 IS
and Keycloak facades support the same methods.


> Integrate Keycloak with PGA
> ---------------------------
>
>                 Key: AIRAVATA-2342
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2342
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway, Security
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>             Fix For: 0.18
>
>
> Integrate Keycloak with PGA. Essentially, replace WSO2 IS with Keycloak.
> The initial motivating use case is integration of Keycloak with CILogon.



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

Mime
View raw message