[
https://issues.apache.org/jira/browse/OOZIE-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587942#comment-13587942
]
Hadoop QA commented on OOZIE-1233:
----------------------------------
Testing JIRA OOZIE-1233
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: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: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:red}WARNING: the current HEAD has 2 RAT warning(s), they should be
addressed ASAP{color}
{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:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:red}-1{color} the patch seems to introduce 2 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:green}+1 TESTS{color}
. Tests run: 1025
{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}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/346/
> Add ability to configure Oozie to use HTTPS (SSL)
> -------------------------------------------------
>
> Key: OOZIE-1233
> URL: https://issues.apache.org/jira/browse/OOZIE-1233
> Project: Oozie
> Issue Type: New Feature
> Components: security
> Affects Versions: trunk, 3.3.2
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: OOZIE-1233.patch, OOZIE-1233.patch, OOZIE-1233.patch
>
>
> It's currently possible to configure Oozie to use HTTPS (SSL), but:
> # There isn't a standard way of configuring it
> # It can involve editing settings that users normally don't, including web.xml
> # There's no documentation; using a self-signed certificate with the Oozie
> client is particularly tricky
> We should add an argument to the oozie-setup.sh script that'll configure
> Oozie to use HTTPS so that its easy to do and there's a standard way that
> users will do 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
