[NIFI-7804] Dependencies ending up in nifi-standard-services-api

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.10.0, 1.11.0, 1.12.0, 1.11.1, 1.11.2, 1.11.3, 1.11.4
• Fix Version/s: 1.13.0, 1.12.1
• Assignee: Andy LoPresto
• Reporter: Bryan Bende
• Created: 11/Sep/20 20:44
• Updated: 19/Jul/21 19:35
• Resolved: 17/Sep/20 16:54

Description

One of the changes in https://issues.apache.org/jira/browse/NIFI-7407 was a refactoring to the SSLContextService interface which added classes from nifi-security-utils. The result is that nifi-standard-services-api-nar now has transitive dependencies of nifi-security-utils included...

bcpkix-jdk15on-1.66.jar
bcprov-jdk15on-1.66.jar
bcrypt-0.9.0.jar
bytes-1.3.0.jar
commons-codec-1.14.jar
commons-lang3-3.9.jar 

This means any NAR that has a parent of nifi-standard-services-api-nar, which is most of them, now has these on the classpath which may conflict with versions of the same libraries used in the child NAR.

We should come up with a way to not depend on nifi-security-utils, or split it up into more isolated modules so that these dependencies don't get brought in to the service APIs.

Issue Links

• relates to: NIFI-6563 Add support for TLSv1.3 when running on Java 11
• relates to: NIFI-7802 Unable to create a PropertiesFileLookupService controller service in version 1.12.0
• links to: GitHub Pull Request #4533