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

Posted to dev@openwebbeans.apache.org by "Mark Struberg (Jira)" <ji...@apache.org> on 2026/05/07 19:58:00 UTC

[jira] [Resolved] (MEECROWAVE-347) TLS configuration broken in 2.0.0

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

Mark Struberg resolved MEECROWAVE-347.
--------------------------------------
    Resolution: Fixed

> TLS configuration broken in 2.0.0
> ---------------------------------
>
>                 Key: MEECROWAVE-347
>                 URL: https://issues.apache.org/jira/browse/MEECROWAVE-347
>             Project: Meecrowave
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>            Priority: Major
>             Fix For: 2.1.0
>
>
> It seems that the sslhostconfig does not work anymore with more recent Tomcat Versions. I did not investigate when it broke, but somewhen between tc9 and 11 the certificate related attributes got moved from {SSLHostConfig} to an own class {SSLHostConfigCertificate} and is now 1:n on the hostConfig.
> We need to map this different.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)