[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080962#comment-16080962
]
ASF GitHub Bot commented on NIFI-2528:
--------------------------------------
Github user m-hogue commented on the issue:
https://github.com/apache/nifi/pull/1986
@trkurc and @jskora : After working through a few test cases, I have a
proposal i'd like your thoughts on.
What if we allow the user to select any SSL protocol available through the
UI, but throw an exception with a message explaining why if the processor
doesn't support that protocol. In the ListenHTTP case, Jetty has some SSL
protocols and ciphers disabled by default that may be available to the JVM.
There are two reasons i wouldn't want to tweak ListenHTTP to allow any
configured protocol. 1) It changes the processor behavior since those
Jetty-disabled protocols wouldn't have worked previously anyway and 2) it
possibly opens another can of worms with cipher suite configuration since Jetty
has a set of ciphers disabled by default as well.
Thoughts?
> 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)
