All,

We have 2 systems, one running 1.15.1 and one running 1.16.3.

We have tried to use the nifi.security.autoreload.enabled=true feature and
not had it work in the past and then suddenly yesterday on the 1.16.3
system it WORKED but we can't figure out why.

In this case it WORKED when we accidentally copied in a truststore that had
been set up as JKS and the config was asking for PKCS12, so it failed.

So we tried again on the 1.15.1 system, and while we get the Scanner
entries that appear to notice the change, nothing actually happens.

I quickly went through the release notes and searched here but didn't find
anything specific about changes to improve this.

Any suggestions? We would LOVE to pick up a new truststore but at this
point, we can't figure out how to kick off the change.

log entry example of the scanner:

Sep  9 16:36:46 prod-sts-1 nifi_1|bcf752078c86[2247]: 2022-09-09
16:36:46,644 INFO [Scanner-0] o.e.jetty.util.ssl.SslContextFactory
x509=X509@6f0da1a2(1,h=[prod-sts-1, prod-sts-1.internal, prod-sts-1.com,
sts-prod.company.net],a=[],w=[]) for Server@621d9971
[provider=null,keyStore=file:///opt/nifi/nifi-current/conf/ssl/nifi-keystore.jks,trustStore=file:///opt/nifi/nifi-current/conf/ssl/nifi-truststore.jks]


Dave

Reply via email to