Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-8220

Establish a secure by default configuration for NiFi

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Epic
    • Status: Open
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.14.0
    • Component/s: Tools and Build
    • Labels:
      None
    • Epic Name:
      Secure by Default
    • Epic Status:
      To Do

      Description

      Inspired by this tweet https://twitter.com/_escctrl_/status/1359280656174510081?s=21 and the resulting discussion here https://lists.apache.org/thread.html/rc590f21807192a0dce18293c2d5b47392a6fd8a1ef26d77fbd6ee695%40%3Cdev.nifi.apache.org%3E

      It is time to change our config model. It was also setup to be easy to use. We've seen these silly setups on the Internet before but has gotten ridiculous. We need to take action.

      Will create a set of one or more JIRAs to roughly do the following.
      1. Disable HTTP by default. If a user wants to enable to it for whatever reason then also make them enable a new property which says something to the effect of 'allow completely non secure access to the entire nifi instance - not recommended'
      2. Enable HTTPS with one way authentication by default which would be the client authenticating the server whereby the server has a server cert. We could either make that cert a self-signed (and thus not trusted by client's by default) cert or give a way for the user to run through command line process to make a legit cert.
      3. If not already configured with an authorization provider supply and out of the box provider which supports only a single auto generated at first startup user/password enabling access to the NiFi system.
      4. Disable all restricted processors by default. Require the user to explicitly enable them.

        Attachments

        There are no issues in this epic.

          Activity

            People

            • Assignee:
              joewitt Joe Witt
              Reporter:
              joewitt Joe Witt

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 9h 50m
                9h 50m

                  Issue deployment