[
https://issues.apache.org/jira/browse/OOZIE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17395395#comment-17395395
]
Igor Dvorzhak commented on OOZIE-3632:
--------------------------------------
Hey [~dionusos],
I cloned OOZIE-3599 just because I can not attach patch files to OOZIE-3599 and
kick off CI on them, so to test my changes somehow I cloned OOZIE-3599 (GitHub
PRs also lack CI integration).
If there a way to give me permission to submit patches to OOZIE-3599 then this
will be ideal and I will not need this Jira.
Sure, I can use the same Jetty version as Hadoop uses.
> Upgrade Jetty to 9.4
> --------------------
>
> Key: OOZIE-3632
> URL: https://issues.apache.org/jira/browse/OOZIE-3632
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 5.2.1
> Reporter: Igor Dvorzhak
> Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-3632.patch
>
>
> Jetty could be upgraded to the latest version, which is now 9.4.28.v20200408,
> though it has to be checked before if its feasible.
> In case we upgrade we have to be aware of wildcard certs with SAN as well and
> should change the code to use SslContextFactory.server instead of
> SsslContextFactory in org.apache.oozie.server.SSLServerConnectorFactory class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
