RE: Tomcat 8.5.16 - can't use Java keystore with multiple entries having different keypass for each entry?

2017-07-05 Thread Frank Taffelt
> I don't think that will work because you can't read the key out of the > keystore. The keystore API has the getKey(alias,keypass) method that should give you the key. copying the entry could be: KeyStore newks = KeyStore.getInstance("JKS"); newks.load(null, null); newks.setKeyEntry(alias,

RE: Tomcat 8.5.16 - can't use Java keystore with multiple entries having different keypass for each entry?

2017-07-04 Thread Frank Taffelt
Hi Thomas, > By far the simplest solution is to have one keystore per private key. so maybe this could go into the docs section. > I find the JSSE API tricky to navigate at the best of times so it is possible > I have missed something. If I have, feel free to point me in the right > direction.

RE: Tomcat 8.5.16 - can't use Java keystore with multiple entries having different keypass for each entry?

2017-07-03 Thread Frank Taffelt
Hi Christopher, > > # create 2 entries with different keypass for each entry keytool > > -genkeypair -alias tomcat1 -storepass storepass -keystore > > different.jks -keyalg RSA -keypass tomcat1 -ext san=dns:tomcat1 > > -dname CN=tomcat1 keytool -genkeypair -alias tomcat2 -storepass > >

Tomcat 8.5.16 - can't use Java keystore with multiple entries having different keypass for each entry?

2017-06-30 Thread Frank Taffelt
Hi all, while playing with some ssl setups i stumbled upon the following behaviour that seems like bug to me ? As long as all keyentries in a keystore have the same password all is fine. Using entries with different password tomcat doesnt startup. For testing: At first create 2 different

RE: InvocationTargetException on startup after upgrade to 8.5.13

2017-04-26 Thread Frank Taffelt
>I can't reproduce this. It may be configuration related. Please provide the >steps minimal to reproduce this from a clean 8.5.14 install. http://www.glesir.de/~frank/tomcat-startup.zip Sample CATALINA_BASE structure with a prebuilt webapp. To run it you have to adjust the contained

RE: InvocationTargetException on startup after upgrade to 8.5.13

2017-04-25 Thread Frank Taffelt
>Fixed in 9.0.x and 8.5.x for the next release of each. > after upgrading to 8.5.14 the issue still occurs: INFO: Starting Servlet Engine: Apache Tomcat/8.5.14 Apr 25, 2017 1:57:21 AM org.apache.tomcat.util.IntrospectionUtils getProperty WARNING: IntrospectionUtils: InvocationTargetException for

RE: InvocationTargetException on startup after upgrade to 8.5.13

2017-04-03 Thread Frank Taffelt
and SSLHostConfigCertificate objects via JMX. Frank -Original Message- From: Rémy Maucherat [mailto:r...@apache.org] Sent: Monday, April 03, 2017 11:10 AM To: Tomcat Users List Subject: Re: InvocationTargetException on startup after upgrade to 8.5.13 2017-04-03 10:51 GMT+02:00 Frank

InvocationTargetException on startup after upgrade to 8.5.13

2017-04-03 Thread Frank Taffelt
after upgrading from 8.5.12 to 8.5.13 the following exception is thrown on startup. WARNING: IntrospectionUtils: InvocationTargetException for class org.apache.coyote.http11.Http11NioProtocol ciphers) java.lang.reflect.InvocationTargetException at

RE: AW: wrong request.getServerPort value reported on upgraded HTTP/2 connector ?

2016-06-29 Thread Frank Taffelt
: > On 29/06/2016 07:50, Frank Taffelt wrote: >> i have no other connectors than the one on port 443. > > I can reproduce this. I'll look at getting this fixed for the next release. Fixed. The fix will be in 9.0.0.M9 onwards and 8.5.4 onwards. Mark > > Mark > > >>

AW: wrong request.getServerPort value reported on upgraded HTTP/2 connector ?

2016-06-29 Thread Frank Taffelt
connector ? -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frank, On 6/28/16 11:02 AM, Frank Taffelt wrote: > Calling the method request.getServerPort() returns 80 on http/2 > upgraded requests for the https connector. I would expect that this > method should return 443 in these calls. M

wrong request.getServerPort value reported on upgraded HTTP/2 connector ?

2016-06-28 Thread Frank Taffelt
Calling the method request.getServerPort() returns 80 on http/2 upgraded requests for the https connector. I would expect that this method should return 443 in these calls. My current workarround is to disable the APR Listener as this results in correct value for the https connector. So is this