Matt, you may want to download a newer version of java and grab the latest cacerts file from it. If it is a Verisign cert, it should have work out-of-the-box, unless the root Verisign cert that signed your intermediate cert is not part of your cacerts file. Theoretically, just getting the Verisign root cert should do the trick. I've never tried that before, but basically, the main cert says it is signed by the intermediate cert which is signed by the Verisign root. As long as the Verisign root is in your keystore, it should work because then you trust that one and everything else is connected... Hmm... Ideas....
On Tue, Jul 24, 2012 at 10:21 AM, Peter J. Farrell <[email protected]>wrote: > Matthew Woodward said the following on 07/24/2012 11:16 AM: > > Other weird thing is I didn't get errors when I imported the certs, but I >> don't see them in the list when I do a list using keytool either. >> > I had this problem when I had OpenJVM and SunJVM install on the same > system. Be sure that you use a full path to your cert store (see my > previous email) and that you are using the keytool bundled with the JVM of > your target cert store. I was using the OpenJVM keytool but targeting the > SunJVM cert store -- it looks like it works, but doesn't. > > The reason why I mention this is you stated that the keytool list doesn't > show the imported certs....I'm guessing it was imported into the wrong cert > store. > > > -- > Peter J. Farrell > OpenBD Steering Committee / Mach-II Lead Developer > [email protected] > [email protected] > http://blog.maestropublishing.**com <http://blog.maestropublishing.com> > Identi.ca / Twitter: @maestrofjp > > -- > online documentation: http://openbd.org/manual/ > http://groups.google.com/**group/openbd?hl=en<http://groups.google.com/group/openbd?hl=en> > -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en
