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

NiFiHostnameVerifier should be replaced

    XMLWordPrintableJSON

    Details

      Description

      The NiFiHostnameVerifier does not handle wildcard certificates or complex SubjectAlternativeNames. It should be replaced with a more full-featured implementation, like OkHostnameVerifier from okhttp or DefaultHostnameVerifier from http-client. Either of these options requires introducing a new Maven dependency to nifi-commons and requires further investigation.

      *Note: * the sun.net.www.protocol.httpsDefaultHostnameVerifier simply returns false on all inputs and is not a valid solution.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                thenatog Nathan Gough
                Reporter:
                alopresto Andy LoPresto
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: