You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Jody DesRoches (JIRA)" <ji...@apache.org> on 2018/10/25 17:54:00 UTC
[jira] [Commented] (NIFI-5754) bootstrap.conf not found in
NiFiPropertiesLoader with custom conf.dir value
[ https://issues.apache.org/jira/browse/NIFI-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664089#comment-16664089 ]
Jody DesRoches commented on NIFI-5754:
--------------------------------------
Work around is to keep a copy of bootstrap.conf in $NIFI_HOME/conf and conf.dir/ but I haven't tested how that would be affected by running encrypt-config.sh. Where will the hexkey actually be stored?
> bootstrap.conf not found in NiFiPropertiesLoader with custom conf.dir value
> ---------------------------------------------------------------------------
>
> Key: NIFI-5754
> URL: https://issues.apache.org/jira/browse/NIFI-5754
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management
> Affects Versions: 1.7.1
> Environment: N/A
> Reporter: Jody DesRoches
> Priority: Major
>
> Issue in NiFiPropertiesLoader when trying to find "nifi.bootstrap.sensitive.key="
> When starting the nifi service, $NIFI_HOME/conf/bootstrap.conf is used. When NiFiPropertiesLoader attempts to decrypt nifi.properties it guesses that bootstrap.conf exists in the same directory as nifi.properties. This is not true if "conf.dir" has been defined in bootstrap.conf.
> Apparent problem is on NiFiPropertiesLoader line 113. Method extractKeyFromBootstrapFile() should call extractKeyFromBootstrapFile("$NIFI_HOME/conf/bootstrap.conf") by default as the method comment indicates. Instead it calls this method with an empty string resulting in an IOException on service startup if the conf.dir has been customized.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)