You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Attila Sasvari (JIRA)" <ji...@apache.org> on 2016/12/27 12:02:58 UTC

[jira] [Assigned] (OOZIE-2756) Extend HTTPS configuration settings for embedded Jetty

     [ https://issues.apache.org/jira/browse/OOZIE-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Attila Sasvari reassigned OOZIE-2756:
-------------------------------------

    Assignee: Attila Sasvari

> 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
>
> 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)