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

Allow usage of Trusted Hostname on all HTTP-accessing processors

    XMLWordPrintableJSON

    Details

    • Type: Wish
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.7.1
    • Fix Version/s: None
    • Component/s: Core Framework
    • Labels:

      Description

      I've used several PutHTTP and GetHTTP processors in a workflow for development before realizing that I cannot configure a Trusted Hostname property for those like I can for InvokeHTTP. Configuration and setup limitations of the SSLContextService have me wanting to avoid it at all costs.

      I think the workaround is to use InvokeHTTP in place of the others but it'd be nice to be able to set a trusted hostname anywhere that an SSLContentService can be used.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                alopresto Andy LoPresto
                Reporter:
                colindean Colin Dean
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: