[
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
{code}
<property>
<name>oozie.service.AuthorizationService.security.enabled</name>
<value>true</value>
<description>
Specifies whether security (user name/admin role) is enabled or not.
If disabled any user can manage Oozie system and manage any job.
</description>
</property>
{code}
Based on the oozie docs this is the new property
http://oozie.apache.org/docs/4.0.0/AG_Install.html
{code}
Oozie security is set via the following configuration property (default value
shown):
oozie.service.AuthorizationService.security.enabled=false
{code}
> 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
(v6.1#6144)
