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

Configuring Oozie for HTTPS still allows HTTP connections to all resources

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

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • None
    • 4.0.0
    • security
    • None

    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.

      Attachments

        1. OOZIE-1414.patch
          1 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