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-2889) Use service account to authenticate Django portal to IamAdminService
Date Fri, 02 Nov 2018 20:55:02 GMT

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

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

Commit 9cb5742efe2ce567cf775156c138137c809d3c86 in airavata's branch refs/heads/develop from
[~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=9cb5742 ]

AIRAVATA-2889 Add manage-users role to web service account

Also adding the Django callback url automatically.


> Use service account to authenticate Django portal to IamAdminService
> --------------------------------------------------------------------
>
>                 Key: AIRAVATA-2889
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2889
>             Project: Airavata
>          Issue Type: Improvement
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> PGA uses the realm admin's username and password, but it would be better if we could
just use the existing client_id and client_secret to get an access token for authenticating
with the IAM Admin Services API.
> h5. TODO
> * [ ] Add *manage-users* role from the *realm-management* client to the automatically
generated PGA client in the tenant creation code
> * [ ] Use ProfileService to get oauth client id/seagrid from TenantProfileService instead
of from Gateway in workspace catalog (where it may or may not be populated)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message