[OOZIE-1414] Configuring Oozie for HTTPS still allows HTTP connections to all resources

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 4.0.0
• Component/s: security
• Assignee: Robert Kanter
• Reporter: Robert Kanter
• Created: 13/Jun/13 17:45
• Updated: 31/Aug/13 00:02
• Resolved: 14/Jun/13 17:17

Description

When you run oozie-setup.sh prepare-war -secure it is supposed to replace server.xml with ssl-server.xml (in the oozie-server/conf/ dir) and web.xml with ssl-web.xml (in the WAR file).

OOZIE-670 changed oozie-setup.sh to prepare the war file without calling addtowar.sh. However, the code added by OOZIE-1233 and OOZIE-1268 still delegates replacing web.xml with ssl-web.xml to addtowar.sh, which oozie-setup.sh no longer calls.

Therefore, when you try to configure Oozie for HTTPS, it will use the original web.xml file; which means that all resources are accessible from both HTTPS and HTTP.

This isn't an issue in Oozie 3.3.2 because it didn't include OOZIE-670, so addtowar.sh was still called.

Issue Links

• is broken by: OOZIE-670 Merge addtowar and oozie-setup scripts into one
• is related to: OOZIE-1268 Configuring Oozie to use SSL doesn't work if addtowar.sh is invoked directly
• is related to: OOZIE-1233 Add ability to configure Oozie to use HTTPS (SSL)