[NIFI-7223] NiFi fails to start correctly when keystorePasswd is filled and keyPasswd is blank

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.12.0, 1.11.4
• Assignee: Nathan Gough
• Reporter: Nathan Gough
• Created: 04/Mar/20 16:17
• Updated: 16/Mar/20 16:48
• Resolved: 16/Mar/20 16:48

Description

A secure NiFi will start up but will throw exceptions on attempting to access the UI. This is due to a change in NIFI-6927

For a keystore and key with matching passwords, when the keystorePasswd property in nifi.properties is set, and the keyPasswd is not, the OkHttpReplicationClient would receive "" for the keyPasswd instead of null, causing the OkHttpReplicationClient and NiFi to still initialize but not run correctly. Historical usage suggests the OkHttpReplicationClient should use the keystorePasswd value.

Issue Links

• is caused by: NIFI-6927 PutElasticsearchHttp 1.10.0 with java 11 Fails to initialize due to "clientBuilder.sslSockerFactory(SSLSocketFactory) not supported on JDK 9+
• is duplicated by: NIFI-7219 Authentication fails if nifi.security.keyPasswd is empty
• is related to: NIFI-7219 Authentication fails if nifi.security.keyPasswd is empty
• links to: GitHub Pull Request #4144
• links to: GitHub Pull Request #4145