falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-212) OozieClient does not propagate user in request to Oozie server
Date Wed, 20 Nov 2013 02:55:21 GMT

    [ https://issues.apache.org/jira/browse/FALCON-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827262#comment-13827262

Arpit Gupta commented on FALCON-212:

We are actually setting this property

     Specifies whether security (user name/admin role) is enabled or not.
     If disabled any user can manage Oozie system and manage any job.

Based on the oozie docs this is the new property


Oozie security is set via the following configuration property (default value shown):


> OozieClient does not propagate user in request to Oozie server
> --------------------------------------------------------------
>                 Key: FALCON-212
>                 URL: https://issues.apache.org/jira/browse/FALCON-212
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: oozie
>    Affects Versions: 0.3
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>            Priority: Blocker
>             Fix For: 0.4
>         Attachments: FALCON-212.patch
> All the lifecycle management functions on entity or instance fails with authorization
error as user is null. Falcon depends on org.apache.oozie.client.OozieClient to interact with
Oozie which does not propagate the user info in the request. 
> I plan to add the user in request to the URL before making a connection in org.apache.oozie.client.CustomOozieClient.

This message was sent by Atlassian JIRA

View raw message