[
https://issues.apache.org/jira/browse/ATLAS-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878682#comment-16878682
]
ASF subversion and git services commented on ATLAS-3153:
--------------------------------------------------------
Commit 645bc94e59969d08b81e7af7a5a2db78207ab3fe in atlas's branch
refs/heads/master from Bolke de Bruin
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=645bc94 ]
ATLAS-3153 :- Add Keycloak authentication method to Atlas.
Keycloak is an open source Identity and Access Management solution aimed at
modern applications and services. It makes it easy to secure applications and
services with little to no code.
This enabled Atlas to use OpenID Connect (OAUTH2) and allows integration with
more services.
Signed-off-by: nixonrodrigues <[email protected]>
> Support OpenID Connect directly rather than through Knox
> --------------------------------------------------------
>
> Key: ATLAS-3153
> URL: https://issues.apache.org/jira/browse/ATLAS-3153
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core, atlas-webui
> Affects Versions: 2.0.0
> Reporter: Bolke de Bruin
> Priority: Major
> Labels: authentication, authorization
> Attachments: 0001-ATLAS-3153-Add-keycloak-authentication.patch,
> application.log, keycloak.json, openid_connect_atlas.md
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The current SSO implementation with Apache Knox is limiting SSO
> interoperability to Apache Knox. Knox uses JWT verification which could
> easily be extended to allow for direct OpenID Connect support and doesn't
> require organizations to deploy Knox.
> Required changes:
> * Pickup bearer token from headers
> * Improve and standardize redirecting
> * Optionally: obtain certificates from well_known uri
> * Optionally: obtain user groups from userinfo endpoint rather than UGI
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
