[
https://issues.apache.org/jira/browse/OOZIE-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811379#comment-15811379
]
Abhishek Bafna commented on OOZIE-2756:
---------------------------------------
I think, Currently it is preventing accidental changes in property and catching
them using the testcase.
The other way to look at it is, if the user changes the main code (including
oozie conf files) then need not to worry about testcase, because it will pick
it up updated property. But I think preventing/detecting wrong property change
by user is a different aspect then testing the value of a given property. :)
> 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,
> OOZIE-2756-03.patch, OOZIE-2756-04.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)
