[
https://issues.apache.org/jira/browse/OOZIE-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15804557#comment-15804557
]
Abhishek Bafna commented on OOZIE-2756:
---------------------------------------
[~asasvari] minor things:
* configuration properties can be defined as Constants and re-use them into
test cases. e.g {{oozie.https.exclude.cipher.suites}},
{{testConfig.set("oozie.https.truststore.file", "test_truststore_file");}}
* The default configuration values can be checked in the
{{TestConfigurationService}}.
> Extend HTTPS configuration settings for embedded Jetty
> ------------------------------------------------------
>
> Key: OOZIE-2756
> URL: https://issues.apache.org/jira/browse/OOZIE-2756
> Project: Oozie
> Issue Type: Improvement
> Reporter: Attila Sasvari
> Assignee: Attila Sasvari
> Attachments: OOZIE-2756-01.patch, OOZIE-2756-02.patch
>
>
> Regarding HTTPS settings, currently Oozie only support
> {{oozie.https.include.protocols}} and {{oozie.https.exclude.cipher.suites}}
> (introduced by OOZIE-2666).
> However, Jetty SslContextFactory supports the following configurations:
> * excludeProtocols
> * includeProtocols
> * excludeCipherSuites
> * includeCipherSuites
> To have more control over employed protocols and cipher suites, we should
> extend current implementation to allow users to configure
> {{excludeProtocols}} and {{includeCipherSuites}}. Sensible defaults are also
> needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
