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.