BBC8wLTArBggrBgEFBQcwAYYfaHR0cDovL3d3dy5pbGV4LmZyL29jc3Avb2NzcHNydjANBgkqhkiG9w0BAQUFAAOBgQAibTBDEuEvihNSwSuI5Gncm2OJUBPFVdCgN0ESuHnLkrglLG8+JNUaUZFZtDBMY8YzgCDPwEjya27ofRuJg69Op1KBvH77y3xVOAe3tikby0Xs0/U5FPp1Jo0xlczyLZz1C5UBraJRFr6JEsyImE9+r9GGp4va7FptAtuSdvqW1Q==PhoahxIVk7XktcsO9/jVFzARACBhgTTck8rH3mHoGItxE8RmNqkjo6xxDNIql0tGZUrzPRcvyTcDGnFHaqT1
to create your own URIDereferencer implementation
for resolving RetrievalMethod URIs (of any type).
--Sean
Julien TAUPIN wrote:
> Hi All
>
> I work with java xmlsecurity 2.1.
>
> I would like to know to get the EncryptedKey designed by in URI in a
> in RetrievalMethod el
Hi all,
I try to perform an XML encryption of data by a secret key. In the w3c
recommendations it is precised that the initialisation vector IV must be
transmit but does not specified where : "the IV, if any, could be specified
as being with the cipher data, as an algorithm content element, or
els
.org
Objet : Re: Initialisation vector
Julien TAUPIN wrote:
> Hi all,
>
> I try to perform an XML encryption of data by a secret key. In the w3c
> recommendations it is precised that the initialisation vector IV must
> be transmit but does not specified where : "the IV, if
Hi all,
Is it possible to use the XML Security API with a JCA / JCE provider which
is not the default provider.
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.
@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 prov
I have found how to select my provider :
JCEMapper.setProviderId(myprovider.getName());
-Message d'origine-
De : Julien TAUPIN [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 21 septembre 2005 09:05
À : security-dev@xml.apache.org
Objet : RE: Using XMLSecurity with a JCA provider
Hi all,
I'm sorry to insist but I do not understand why my modifications on
SignatureDSA do not have been accepted.
For the moment, during RSA signature we get the JCA Signature object from
the provider defined with JCEMapper.setProviderID(providerName);
This is done in the
org.apache.xml.sec
d'origine-
De : Vishal Mahajan [mailto:[EMAIL PROTECTED]
Envoyé : mardi 27 septembre 2005 11:51
À : security-dev@xml.apache.org
Objet : Re: Using XMLSecurity with a JCA provider other than default one
Did you try using the Security.insertProviderAt method?
Vishal
Julien TAUPIN wrote:
>I
her than default one
Can you send me the relevant part of the stack overflow trace? I am curious
about this problem but I need to see more details.
Thanks,
Sean
Julien TAUPIN wrote:
> Yes but the problem is that if I place my Provider on the first
> position the Sun jarverifier failed when i
I use this method to specify my JCE provider.
So I raise my hands !!
But if another way to select my provider exists (except placing it at the
first rank in the provider list), I can change my code
-Message d'origine-
De : Raul Benito [mailto:[EMAIL PROTECTED]
Envoyé : samedi 22 octobr
|| "".equals(BaseURI)) {
return new URI(uri);
}
return new URI(new URI(BaseURI), uri);
}/
I think that the getNewURI() method should be used in the
ResolverLocalFilesystem class.
--
*Julien TAUPIN*
*Ingénieur d'études *
Ilex
51, boulevard Volta
to use ?
Should I always use an empty BaseURI to generate XMLDsig signatures
which would follow the XMLDsig specifications ?
Thanks
--
*Julien TAUPIN*
*Ingénieur d'études *
Ilex
51, boulevard Voltaire
92600 Asnières-sur-Seine
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>*
Té
13 matches
Mail list logo