pported if
> the following property is set in oozie-site.xml :
>
> oozie.service.AuthorizationService.default.group.as.acl=true
>
> So you can define Oozie ACL-s similar to Hadoop ACLs using oozie.job.acl
> property in your workflows' configuration .
>
> For more information:
> -
> https://oozie.apache.org/docs/4.3
old ACL model where a group was provided is still supported if
the following property is set in oozie-site.xml :
oozie.service.AuthorizationService.default.group.as.acl=true
So you can define Oozie ACL-s similar to Hadoop ACLs using oozie.job.acl
property in your workflows' configuration .
Hi,
Wondering if there is a way to define ACLs so that a user can
start/stop/kill a workflow launched by another user (in kerberized cluster)?
The use case is the following: users a, b and c are working on a project X
and a business user has been created for project A. This business user is
used
