[jira] [Commented] (OOZIE-1376) Extending Oozie ACLs like admin groups and proxy users to support both groups and users

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on OOZIE-1376:
----------------------------------

Testing JIRA OOZIE-1376

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 132
.    {color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:red}-1 COMPILE{color}
.    {color:red}-1{color} HEAD does not compile
.    {color:red}-1{color} patch does not compile
.    {color:red}-1{color} the patch seems to introduce 1 new javac warning(s)
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.    Tests run: 1792
.    Tests failed: 8
.    Tests errors: 21

.    The patch failed the following testcases:

.      testCoordStatusTransitServiceSuspendedWithError(org.apache.oozie.service.TestStatusTransitService)
.      testBundleStatusCoordSubmitFails(org.apache.oozie.service.TestStatusTransitService)
.      testCoordMaterializeTriggerService3(org.apache.oozie.service.TestCoordMaterializeTriggerService)
.      testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.      testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
.      testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.      testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.      testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)

{color:red}-1 DISTRO{color}
.    {color:red}-1{color} distro tarball fails with the patch

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3127/

> Extending Oozie ACLs like admin groups and proxy users to support both groups and users
> ---------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1376
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1376
>             Project: Oozie
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: trunk
>            Reporter: Kai Zheng
>            Assignee: Kai Zheng
>              Labels: Security
>             Fix For: trunk
>
>         Attachments: OOZIE-1376.patch
>
>
> Currently Oozie relevant ACLs supports only users in some case or only groups in other case, which is not consistent with other components like Hadoop, HBase and Hive. Supporting both users and groups in ACLs can simplify the admin configuration work, and also help implement more advanced access control such as RBAC based on the ACLs scheme. For example RBAC can simply translate role privilege into corresponding ACLs with the users and groups assigned to the role.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)