gobblin-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hung Tran (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GOBBLIN-634) Gobblin as a Service needs to know who sends the request
Date Tue, 27 Nov 2018 02:57:00 GMT

     [ https://issues.apache.org/jira/browse/GOBBLIN-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hung Tran resolved GOBBLIN-634.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 0.14.0

Issue resolved by pull request #2504
[https://github.com/apache/incubator-gobblin/pull/2504]

> Gobblin as a Service needs to know who sends the request
> --------------------------------------------------------
>
>                 Key: GOBBLIN-634
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-634
>             Project: Apache Gobblin
>          Issue Type: New Feature
>            Reporter: Kuai Yu
>            Assignee: Kuai Yu
>            Priority: Major
>             Fix For: 0.14.0
>
>
> Today GaaS doesn't know who sends the request. The aim of this ticket is to provide a
basic abstraction which can be extended by LinkedIn internal authentication / authorization
framework. Those abstractions includes
> 1) How to obtain a requester and
> 2) How to describe a service a requester
>  
>  



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

Mime
View raw message