PKCS#8 encryption algorithm unrecognized

2024-03-19 Thread Timothy Resh
where the . is the fqdn This works fine *until* Tomcat 9.0.83 and now we get the following listed below. I have read some of the https://bz-he-de.apache.org/bugzilla/show_bug.cgi?id=67675 bugs and ask for help. The certificates are being created using openssl 3.013. Please note the encrypte

Re: PKCS#8 encryption algorithm unrecognized

2024-03-25 Thread Timothy Resh
" -storepass "changeit" -noprompt keytool.exe -delete -alias "WSD-2DNX4M3.mydomain.com" -keystore "C:\tmp12\Certificate\Keystore\Vessel.p12" -storepass "changeit" -noprompt keytool.exe -import -alias "ASA12 SAMM Vessel" -file "C:\tmp12\Client Co

Re: PKCS#8 encryption algorithm unrecognized

2024-04-03 Thread Timothy Resh
Sure, I can provide the entire setup for you. I'll work on that tonight . On Sun, Mar 31, 2024 at 2:05 PM Mark Thomas wrote: > On 25/03/2024 16:56, Timothy Resh wrote: > > Sorry for the delay. Our certificate creation process was automated > > several years ago and I h

Re: PKCS#8 encryption algorithm unrecognized

2024-04-04 Thread Timothy Resh
I got the Object ID and version straight out of the Certificate using Keystore Explorer. I'm not sure why there is a difference. The "\" is because I manually deleted the beginning part of the path. It's correct in the actual file. Java is 1.8. On Wed, Apr 3, 2024 at 6:11 PM Konstantin Kolinko

Re: PKCS#8 encryption algorithm unrecognized

2024-04-04 Thread Timothy Resh
Java is 1.8.0_391 On Thu, Apr 4, 2024 at 1:35 PM Timothy Resh wrote: > I got the Object ID and version straight out of the Certificate using > Keystore Explorer. I'm not sure why there is a difference. > > The "\" is because I manually deleted the beginning part of

Re: PKCS#8 encryption algorithm unrecognized

2024-06-10 Thread Timothy Resh
After much debugging, I have found the issue in my situation. In the server.xml file, you must put keystoreType="PKCS12" for it to recognize the keystore properly. On Fri, Apr 5, 2024 at 4:27 AM Roberto Benedetti < roberto.benede...@dedalus.eu> wrote: > > I got the Object ID and version straight

Re: PKCS#8 encryption algorithm unrecognized

2024-06-25 Thread Timothy Resh
the store properly. So, I tried putting in the keystoreType="PKCS12 and now it works. I hope this helps. I'm still set up for debugging if you need something looked at. Thanks On Tue, Jun 11, 2024 at 2:14 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > M

Re: Openssl Connector configuration for Dynamic Client Authorization does not work.

2025-01-30 Thread Timothy Resh
for all stores and certs. Remember that this is not an SSLHostConfig configuration in the Connector, so Tomcat is using its internally created SSLHostConfig. Thanks for all your help. Regards, Timothy On Wed, Jan 29, 2025 at 4:47 AM Mark Thomas wrote: > On 28/01/2025 17:16, Timothy Resh wr

Re: Openssl Connector configuration for Dynamic Client Authorization does not work.

2025-01-28 Thread Timothy Resh
\SMIS_APP\Certificates\CA\intermediate.ca" SSLCACertificatePath="C:\Vol1\SMIS_APP\Certificates\CA\" I want to ensure I do not get the configuration mismatched when tomcat creates the _default_ SSLHostConfig, as we need those "java.net.ssl.*" properties set for the SOAP c

Re: Openssl Connector configuration for Dynamic Client Authorization does not work.

2025-01-21 Thread Timothy Resh
orp.tomcat.propertysource.MyPropertySource and it sets these keys. Will this force me to JSSE and not OpenSSL, and how does this impact using caCertificatePath? Thanks, On Wed, Jan 15, 2025 at 11:03 AM Christopher Schultz < ch...@christopherschultz.net> wrote: > Timothy, > > O

Re: Openssl Connector configuration for Dynamic Client Authorization does not work.

2025-01-13 Thread Timothy Resh
d not client auth? On Fri, Jan 10, 2025 at 5:33 PM wrote: > Timothy > > > Am 09.01.2025 um 17:15 schrieb Timothy Resh : > > > > The following is a configuration that we have used to set up the Client > > Authorization to work in Tomcat. We use introspection > >

Re: Openssl Connector configuration for Dynamic Client Authorization does not work.

2025-01-14 Thread Timothy Resh
ation in [1598] milliseconds On Mon, Jan 13, 2025 at 1:01 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > Timothy, > > On 1/13/25 9:58 AM, Timothy Resh wrote: > > This system and configuration I inherited and was told it works and it > > should have bee

Openssl Connector configuration for Dynamic Client Authorization does not work.

2025-01-09 Thread Timothy Resh
The following is a configuration that we have used to set up the Client Authorization to work in Tomcat. We use introspection the IntrospectionUtils.PropertySource to decipher the password and set the following environment variables System.setProperty("javax.net.ssl.keyStore", keyStorePath);

Tomcat 9.0.98 Performance hits AWS 100% CPU

2025-03-07 Thread Timothy Resh
Dear Apache Support Team, I'm running Tomcat 9.0.98 in the AWS Cloud. After several days of use, we see that the CPU utilization eventually reaches 100% in the Cloud, but when we RDP into the Server and look at the Task Manager, we do not see the performance being impacted. However, users complain

Re: Tomcat 9.0.98 Performance hits AWS 100% CPU

2025-03-12 Thread Timothy Resh
h...@christopherschultz.net> wrote: > > > Chuck, > > > > On 3/7/25 5:38 PM, Chuck Caldarale wrote: > > > > > >> On 2025 Mar 7, at 16:06, Timothy Resh wrote: > > >> > > >> Dear Apache Support Team, > > >> > > >&

Tomcat Performance from JMX data

2025-06-04 Thread Timothy Resh
ALCON, I have a production server with JMX enabled. However, we cannot install any additional software to do performance monitoring. We can, however, extract data from the MBeans and transfer it elsewhere for analysis. I saw the ant tasks in the Tomcat documentation. Does anyone know of someth