Jessica,
Peter Kreuser
> Am 07.08.2019 um 14:33 schrieb Alten, Jessica-Aileen
> :
>
> Dear all,
>
> I have a problem with the Tomcat 9.0.22 configuration for TLSv1.3 using
> jdk8u222-b10_openj9-0.15.1 on Windows Server 2016. In principle TLSv1.3
> works, but I want to specify the allowed ci
Dear all,
I have a problem with the Tomcat 9.0.22 configuration for TLSv1.3 using
jdk8u222-b10_openj9-0.15.1 on Windows Server 2016. In principle TLSv1.3
works, but I want to specify the allowed cipher suites as well.
The relevant parts of server.xml are:
...
On 07/08/2019 04:51, Jason Wee wrote:
> Hi,
>
> we are using tomcat version 8.5.20 and we encounter the following exceptions
>
> 24-Jul-2019 23:24:45.398 SEVERE [https-jsse-nio-8443-exec-104]
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
> java.lang.IllegalArgumentException
> at
Munzer,
Am 2019-08-07 09:19, schrieb Peter Kreuser:
Hi Munzer,
I guess we‘re going a slightly awkward way here, but to fix your
problem with the new cert in the first place, you could use this:
If your keystore is the old proprietary format, convert it to PKCS12:
keytool -importkeystore -src
Hi Munzer,
I guess we‘re going a slightly awkward way here, but to fix your problem with
the new cert in the first place, you could use this:
If your keystore is the old proprietary format, convert it to PKCS12:
keytool -importkeystore -srckeystore keystore.jks -destkeystore keystore.p12
-dests