You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andy LoPresto (JIRA)" <ji...@apache.org> on 2018/08/07 03:16:00 UTC

[jira] [Assigned] (NIFI-5400) NiFiHostnameVerifier should be replaced

     [ https://issues.apache.org/jira/browse/NIFI-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy LoPresto reassigned NIFI-5400:
-----------------------------------

    Assignee: Nathan Gough

> NiFiHostnameVerifier should be replaced
> ---------------------------------------
>
>                 Key: NIFI-5400
>                 URL: https://issues.apache.org/jira/browse/NIFI-5400
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.7.0
>            Reporter: Andy LoPresto
>            Assignee: Nathan Gough
>            Priority: Major
>              Labels: certificate, hostname, security, tls
>             Fix For: 1.8.0
>
>
> 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. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)