[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099307#comment-16099307
]
ASF GitHub Bot commented on NIFI-2528:
--------------------------------------
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/nifi/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.
> Update ListenHTTP to honor SSLContextService Protocols
> ------------------------------------------------------
>
> Key: NIFI-2528
> URL: https://issues.apache.org/jira/browse/NIFI-2528
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0, 0.8.0, 0.7.1
> Reporter: Joe Skora
> Assignee: Michael Hogue
>
> Update ListenHTTP to honor SSLContextService Protocols as [NIFI-1688] did for
> PostHTTP.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
