Fernando,
Unless you specifically tell it not to, when you initialize JSS, it
installs the JSS provider with the highest precedence. Since the JSS
provider doesn't implement everything that the Sun providers do, that
may be your problem.
CryptoManager.initialize:
967 if( values.installJSSProvider ) {
968 int position = java.security.Security.insertProviderAt(
969 new JSSProvider(), 1);
I use JSS in an application and found that after initializing JSS our
SSL connections stopped working because JSS isn't a JSSE provider (you
need to do SSL a different way with JSS), so I used the
InitializationValues options to not install the JSS provider
automatically, and manually install it at the lowest precedence and
specifically pass the provider name/object to methods when I want to
make sure I'm using JSS. Since the problem I saw is similar to what you
are describing, you could try something similar.
Provider jssProvider = new JSSProvider();
CryptoManager.InitializationValues initializationValues = new
CryptoManager.InitializationValues(jssDbDir);
initializationValues.installJSSProvider = false;
CryptoManager.initialize(initializationValues);
Security.insertProviderAt(jssProvider,Security.getProviders().length);
> CryptoManager.initialize("C:\Documents and
> Settings\Administrador
> \Datos de programa\Mozilla\Firefox\Profiles\ojgat91z.default");
> CryptoManager cm = CryptoManager.getInstance();
> If I delete the first lines 2 all is OK
> I have tested with several jdk and I have obtained the same result
>
Since you don't initialize JSS without those 2 lines, the provider
wouldn't get installed and wouldn't be "getting in the way" of the
CertificateFactory.
> It is a difficult error because the JSS library cause a error in
> execution of javax.security package
Hopefully making the small change I described will help you out.
Good luck,
Dave
_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
