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

Peter Orova commented on OOZIE-3196:
------------------------------------

Hello [~dionusos]!

Thank you for your suggestion. I agree that an ACL like capability would bring 
value, although I believe a better way of doing that would be by providing an 
authorization API that could be used by 3rd party applications. What do you 
think?

> Authorization: restrict world readability by user
> -------------------------------------------------
>
>                 Key: OOZIE-3196
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3196
>             Project: Oozie
>          Issue Type: New Feature
>          Components: bundle, coordinator, workflow
>    Affects Versions: 5.0.0b1, 5.0.0
>            Reporter: Andras Piros
>            Assignee: Peter Orova
>            Priority: Major
>             Fix For: 5.1.0
>
>
> The [*current authorization 
> model*|https://issues.apache.org/jira/browse/OOZIE-228] does not fit the 
> enterprise requirements as everything is readable and writable by everyone by 
> default.
> Write access can be restricted using authorization but restricting read 
> rights is only possible via Yarn ACLs and HDFS rights which still does not 
> prevent accessing the workflow, coordinator or bundle job’s configurations 
> for everyone.
> Improve authorization so it’s possible to configure read/write access for 
> workflows, coordinators, and bundles in a more granular way. Could involve 
> Sentry during implementation or create and design a new system that fits the 
> needs.



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

Reply via email to