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
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
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
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
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
" -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
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
