[jira] [Commented] (KNOX-789) Apache Atlas REST API support

["Larry McCay (JIRA)" <ji...@apache.org>]

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

Larry McCay commented on KNOX-789:
----------------------------------

[~nixonrodrigues] and [~Wancy] - I believe that @wancy is correct regarding the service definition here. We shouldn't provide specifics here unless the defaults will not work.

In this particular case, the use of the Anonymous authentication provider will force it to always use Anonymous which assumes that the back end service will be doing the authentication or just accepting the anonymous user as the identity. This will result in the API not being able to leverage the various authentication and federation providers available in Knox or that can be custom built for deployments.

With that said, I am curious how you will plan to inflow the identity from a proxied request given that Atlas doesn't support the Hadoop trusted proxy pattern?

If we are intending the API to only be used by the Atlas UI then that will likely work as the Atlas specific session cookies and even KnoxSSO cookie will be sent by the PassAllHeaders dispatch.

> Apache Atlas REST API support
> -----------------------------
>
>                 Key: KNOX-789
>                 URL: https://issues.apache.org/jira/browse/KNOX-789
>             Project: Apache Knox
>          Issue Type: New Feature
>         Environment: all
>            Reporter: Jeffrey E  Rodriguez
>            Assignee: Shi Wang
>             Fix For: 0.13.0
>
>         Attachments: 0001-Apache-Atlas-REST-API-support.patch, 0001-KNOX-789-newpatch.patch, KNOX-789.patch
>
>
> Apache REST API support through Knox
> https://atlas.incubator.apache.org/api/rest.html



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