[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099908#comment-16099908
]
ASF GitHub Bot commented on NIFI-2528:
--------------------------------------
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/1986
I don't want to complicate this, but I feel like I must be missing
something.
As much as possible, the validation at configuration time should provide
the user feedback, not failure upon execution. So,
- SSLContextService should only allow selection of supported protocols, if
SSLv3 will not work it should be removed from the list, and
- if we need SSLv3 in some places we either need 2 variations of
SSLContextService like @alopresto mentioned earlier or the ability to configure
and query the security level so processors requiring only the higher security
protocols can invalidate in the GUI (before execution) if provided a less
secure service.
Does that make sense?
> 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)
