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

Isha Lamboo commented on NIFI-13985:
------------------------------------

It seems that this error also occurs when connecting to secure LDAP for the 
LDAP authorizer, preventing NiFi from starting if you use that.


The authorizer settings used successfully in 1.28.0 with only a truststore 
specified did not work in NiFi 2.0.0
After finding this ticket, I copied the truststore location and password to the 
keystore fields in authorizer.xml This worked and I was able to start NiFi  
connect to the LDAP server.

Just leaving this here so anyone else having PKIX pathbuilding or truststore 
issues can find the workaround.

> StandardSSLContextService error for when keystore file is not provided
> ----------------------------------------------------------------------
>
>                 Key: NIFI-13985
>                 URL: https://issues.apache.org/jira/browse/NIFI-13985
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Mark Bean
>            Assignee: Mark Bean
>            Priority: Major
>             Fix For: 2.1.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently, when the Keystore file is not provided in the 
> StandardSSLContextService configuration, a TrustManager not be created.
> {{252         final TrustManager trustManager;}}
> {{253         final String trustStoreFile = {*}getKeyStoreFile{*}();}}
> {{254         if (trustStoreFile == null || trustStoreFile.isBlank()) {}}
> {{255             getLogger().debug("Trust Store File not configured");}}
> {{256         } else {}}
> {{257             trustManager = createTrustManager();}}
> {{258             sslContextBuilder.trustManager(trustManager);}}
> {{259         }}}
> Line 254 should be:
> {{         final String trustStoreFile = {*}getTrustStoreFile{*}();}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to