[
https://issues.apache.org/jira/browse/NIFI-10932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679887#comment-17679887
]
David Handermann commented on NIFI-10932:
-----------------------------------------
Thanks for describing these details [~Chris S]. It sounds like this could be
due to using the Bouncy Castle PKCS12 implementation, which is unable to use
some PKCS12 files as trust stores without a specialized alias property. The JDK
implementation is more robust, so I will look into options.
> NiFi Toolkit CLI cannot connect to NiFi - trustAnchors parameter must be
> non-empty
> ----------------------------------------------------------------------------------
>
> Key: NIFI-10932
> URL: https://issues.apache.org/jira/browse/NIFI-10932
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.19.0, 1.19.1
> Reporter: Chris Sampson
> Priority: Major
> Fix For: 1.20.0
>
>
> When running NiFi 1.19.0 using the {{apache/nifi}} docker image, the NiFi
> Toolkit is not able to connect to the running NiFi instance (with the default
> Single User Auth enabled).
> Having updated the NiFi Toolkit CLI properties file with the Truststore and
> Keystore details generated by NiFi (found within {{nifi.properties}}), then
> attempting to run a command using the NiFi Toolkit command line such as:
> {code:bash}
> /opt/nifi/nifi-toolkit-current/bin/cli.sh session set nifi
> /opt/nifi/nifi-toolkit-current/bin/cli.sh nifi get-services
> {code}
> The following error is returned:
> {quote}
> ERROR: Error executing command 'get-services' : Unexpected error:
> java.security.InvalidAlgorithmParameterException: the trustAnchors parameter
> must be non-empty
> {quote}
> This suggests something isn't working correctly with the NiFi Toolkit JVM
> process/configuration or such (e.g. the correct truststore is not being used,
> see https://www.baeldung.com/java-trustanchors-parameter-must-be-non-empty)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
