You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2013/03/19 20:13:16 UTC
[jira] [Updated] (OOZIE-1233) Add ability to configure Oozie to use
HTTPS (SSL)
[ https://issues.apache.org/jira/browse/OOZIE-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Kanter updated OOZIE-1233:
---------------------------------
Fix Version/s: 4.0.0
> 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
> Fix For: trunk, 3.3.2, 4.0.0
>
> 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