santuario-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julien TAUPIN <julien.tau...@ilex.fr>
Subject RE: Using XMLSecurity with a JCA provider other than default one
Date Wed, 21 Sep 2005 07:04:34 GMT
I thought that the only way to use my own JCA provider was to place it at
the first place of the providers with the following code :

      Provider[] providers = Security.getProviders();
      for(int i=0; i<providers.length; i++)
      {
        Security.removeProvider(providers[i].getName());
      }
      
      Provider myProvider = null;
      Security.addProvider(myProvider);
      for(int i=0; i<providers.length; i++)
      {
        Security.addProvider(providers[i]);
      }

How can I ask XmlSecurity to use an instance of MyProvider without executing
this code ?

For the stack overflow problem it seems that it is a bug in the Sun
JarVerifier. This one use the default provider to verify the signature of
the archive but if the default provider is not the SUN one, it causes the
stack overflow exception.

-----Message d'origine-----
De : Sean Mullan [mailto:Sean.Mullan@Sun.COM] 
Envoyé : mardi 20 septembre 2005 22:34
À : security-dev@xml.apache.org
Objet : Re: Using XMLSecurity with a JCA provider other than default one

Julien TAUPIN wrote:
> Hi all,
> 
> Is it possible to use the XML Security API with a JCA / JCE provider 
> which is not the default provider.

Yes.

> The problem is that I need to use a specific provider but when I 
> define this one as the default provider the jar verifier causes a 
> stack overflow exception.

Could be a bug but more details are needed.

--Sean

Mime
View raw message