[
https://issues.apache.org/jira/browse/OOZIE-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1233:
---------------------------------
Attachment: OOZIE-1233.patch
The changes are mostly in oozie-setup.sh and addtowar.sh; and also
documentation.
If you do oozie-setup.sh prepare-war -secure it will use https; I manually
tested that it works correctly. I only tested with a self-signed certificate,
but a real certificate should also work. I didn't add any unit tests because
the only way to use a self-signed certificate in Java is to add it to a
specific file in your JRE installation, which requires root permission.
> 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
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: 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
