Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1233

Add ability to configure Oozie to use HTTPS (SSL)

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • trunk, 3.3.2
    • 3.3.2
    • security
    • None

    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.

      Attachments

        1. OOZIE-1233.patch
          31 kB
          Robert Kanter
        2. OOZIE-1233.patch
          31 kB
          Robert Kanter
        3. OOZIE-1233.patch
          31 kB
          Robert Kanter

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            rkanter Robert Kanter
            rkanter Robert Kanter
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment