[
https://issues.apache.org/jira/browse/OOZIE-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13528603#comment-13528603
]
Hadoop QA commented on OOZIE-1128:
----------------------------------
Testing JIRA OOZIE-1128
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 1 line(s) with 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 1 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:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{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:green}+1 TESTS{color}
. Tests run: 932
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds 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/248/
> When a user submitting a job is not UNDEF in the request, it should use that
> user as the submitter
> --------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1128
> URL: https://issues.apache.org/jira/browse/OOZIE-1128
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: 3.3.0
> Reporter: Alejandro Abdelnur
> Fix For: 3.3.1
>
> Attachments: OOZIE-1128.patch
>
>
> If Oozie is configured with simple authentication, the user submitting the
> job is taken from the user.name property coming in the request. Which, in the
> case of Oozie Java client and CLI, is the taking from the
> System.getProperties("user.name") property from the client JVM.
> When using another form of authentication, ie Kerberos, if the kerberos
> principal short and the client JVM user.name are the same things work ok.
> However, Oozie throws an E0400 error if they don't match.
> Instead, Oozie should use the authenticated user and override the user in the
> configuration with it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
