Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2108
@alopresto i've verified full clean build w/contrib check. Have ensured
that old flow and new flow works with sensitive values including use of tool to
change sensitive key passphrase and that still
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2108
@alopresto just wanted to ping and see if you forgot to push? I've got
some cycles to test/review it again for a bit if you have it. If not no
problem.
---
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/2108
I rebased against master and am resolving the issues Joe identified above.
Should have a new push shortly.
---
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2108
I have verified that when building an older nifi flow with sensitive
properties I can bring it into the new non-jasypted nifi. So that is great.
I found Jasypt L&N entries in the following
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2108
@alopresto test failures
Tests run: 10, Failures: 0, Errors: 3, Skipped: 4, Time elapsed: 1.727 sec
<<< FAILURE! - in org.apache.nifi.encrypt.StringEncryptorTest
testPBEncryptionShouldBeI
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/2108
You should see output like this when running the commands above:
```
hw12203:...assembly/target/nifi-toolkit-1.4.0-SNAPSHOT-bin/nifi-toolkit-1.4.0-SNAPSHOT
(NIFI-3116) alopresto
