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

Srikanth Venkat commented on ATLAS-3153:
----------------------------------------

[~bolke] This is a good addition. Can you help the community by providing a 
design doc for the use case and the arch. and configs needed for Atlas to 
consume OpenID asserted credentials? Perhaps an interaction diagram to explain 
how this feature will work, the actual flow, and configs needed (for example 
how the user/group mappings are fetched) will be useful to review the patch and 
understand the feature.

Also quick question will a similar mechanism work for Azure AD via OAuth2 
(especially from an authN/authZ perspective) 

> 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
>    Affects Versions: 2.0.0
>            Reporter: Bolke de Bruin
>            Priority: Major
>          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)

Reply via email to