Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1986
I realize that performing this logic (controller service used for listening
vs. outgoing connections) dynamically may be challenging or not possible (CS
can be used by multiple referencing components). This is now leading me to
think we may need to create a new implementation of the
[`SSLContextService`](https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-services/nifi-ssl-context-service-api/src/main/java/org/apache/nifi/ssl/SSLContextService.java#L33-L33)
interface called `ModernSSLContextService` or `IncomingSSLContextService`
which only supports the `TLSv1.2` protocol version. Existing processors would
not change because they can still accept `StandardSSLContextService`, but the
`ListenHTTP` component would only accept this new implementation. It could even
extend `StandardSSLContextService` to delegate most of the code there and
simply override the protocol versions by implementing its own
[`#buildAlgorithmAllowableValues()`](https://github.com/apache/n
ifi/blob/master/nifi-nar-bundles/nifi-standard-services/nifi-ssl-context-bundle/nifi-ssl-context-service/src/main/java/org/apache/nifi/ssl/StandardSSLContextService.java#L473)
method.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
