You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Joe Witt (Jira)" <ji...@apache.org> on 2020/03/10 15:32:00 UTC

[jira] [Commented] (NIFI-7223) NiFi fails to start correctly when keystorePasswd is filled and keyPasswd is blank

    [ https://issues.apache.org/jira/browse/NIFI-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056062#comment-17056062 ] 

Joe Witt commented on NIFI-7223:
--------------------------------

speaking with andy/nathan it sounds like a pr is coming very soon which will restore pre 1.11.3 behavior to remove to regression but still make the improvement.  we should grab this.

> NiFi fails to start correctly when keystorePasswd is filled and keyPasswd is blank
> ----------------------------------------------------------------------------------
>
>                 Key: NIFI-7223
>                 URL: https://issues.apache.org/jira/browse/NIFI-7223
>             Project: Apache NiFi
>          Issue Type: Task
>            Reporter: Nathan Gough
>            Assignee: Nathan Gough
>            Priority: Major
>             Fix For: 1.12.0, 1.11.4
>
>
> A secure NiFi will start up but will throw exceptions on attempting to access the UI. This is due to a change in -NIFI-6927-
> For a keystore and key with matching passwords, when the keystorePasswd property in nifi.properties is set, and the keyPasswd is not, the OkHttpReplicationClient would receive "" for the keyPasswd instead of null, causing the OkHttpReplicationClient and NiFi to still initialize but not run correctly. Historical usage suggests the OkHttpReplicationClient should use the keystorePasswd value.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)