[OOZIE-1233] Add ability to configure Oozie to use HTTPS (SSL)

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk, 3.3.2
• Fix Version/s: 3.3.2
• Component/s: security
• Assignee: Robert Kanter
• Reporter: Robert Kanter
• Created: 21/Feb/13 20:19
• Updated: 20/Jul/13 00:03
• Resolved: 08/Mar/13 01:07

Description

It's currently possible to configure Oozie to use HTTPS (SSL), but:

1. There isn't a standard way of configuring it
2. It can involve editing settings that users normally don't, including web.xml
3. 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.

Issue Links

• is depended upon by: BIGTOP-881 Add support for Oozie to be configured with SSL (HTTPS)
• relates to: OOZIE-1414 Configuring Oozie for HTTPS still allows HTTP connections to all resources
• relates to: OOZIE-1268 Configuring Oozie to use SSL doesn't work if addtowar.sh is invoked directly
• relates to: OOZIE-1257 Make Oozie client automatically redirect from http to https when https is enabled