[
https://issues.apache.org/jira/browse/OOZIE-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107705#comment-14107705
]
Hadoop QA commented on OOZIE-1579:
----------------------------------
Testing JIRA OOZIE-1579
Cleaning local git 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:green}+1{color} the patch does not introduce any trailing spaces
. {color:red}-1{color} the patch contains 2 line(s) longer than 132
characters
. {color:red}-1{color} the patch does not add/modify any testcase
{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:red}-1 TESTS{color}
. Tests run: 1508
. Tests failed: 1
. Tests errors: 0
. The patch failed the following testcases:
. testHiveAction(org.apache.oozie.action.hadoop.TestHiveActionExecutor)
{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/1658/
> Add basic HTTP auth to Oozie CLI
> --------------------------------
>
> Key: OOZIE-1579
> URL: https://issues.apache.org/jira/browse/OOZIE-1579
> Project: Oozie
> Issue Type: Bug
> Components: client
> Reporter: David Wannemacher
> Assignee: David Wannemacher
> Fix For: trunk
>
> Attachments: OOZIE-1579.trunk.2.patch, OOZIE-1579.trunk.patch
>
>
> This proposed change adds Basic HTTP Auth functionality to the Oozie CLI.
> This would never be used in a usual Oozie installation because Oozie servers
> support token-based authentication: Pseudo/Simple Auth and Kerberos.
> Basic HTTP Auth is needed in the Oozie CLI for when the Oozie service is
> placed behind a gateway that uses Basic HTTP Auth over SSL. It is assumed
> that the Oozie service is running with authorization turned off, because the
> gateway is handling authorization. Once the user authenticates himself to the
> gateway, the request is forwarded through the gateway to the oozie service.
> This had to be implemented outside of the custom authentication framework
> provided by Oozie because basic auth requires adding a request property to
> each connection created. It's completely possible that there is a cleaner way
> of implementing this, if so please let me know!
> Two additions were implemented in the CLI:
> * Indication to use Basic Auth. This is done by specifying BASIC as the
> argument to the -auth argument.
> * Configuration of Basic Auth.
> ** Introduction of -username and -password command line arguments.
> ** If the auth mode is BASIC, only -username is provided, and the
> OOZIEPASSWORD environment variable is set, the OOZIEPASSWORD environment
> variable will be used for the password.
> ** If mode is BASIC and only -username is provided, and OOZIEPASSWORD is
> undefined, the user will be prompted for the password, and the shell
> facilities for masking input will be used.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
