There is a patch proposed in Jira that addresses this.
http://issues.apache.org/jira/browse/WSS-45
Short of that, you can implement your own Crypto implementation, which
gets its keystore from memory, and which implements the Crypto interface.
(The proposed patch makes it a bit easier to re-use most of the
AbstractCrypto implementation, without being beholden to reading
keystores off the file system).
I do not know if this patch will be applied to the mainline.
-Fred
p m wrote:
> Hello,
> I don't know how i can encrypt and decrypt a SOAP message with a
> certificate present in memory only (generate dynamicaly) and not on
> hard drive.
>
> I can encrypt without any problems.
> I have an error (NullPointeurException) when i try to decrypt my SOAP
> message.
> The NullPointeurException is because the "property" of my
> org.apache.ws.security.components.crypto.AbstractCrypto is set to
> "null" and there is a call to the method getCertificateFactory() :
> String provider =
> properties.getProperty("org.apache.ws.security.crypto.merlin.cert.provider");
>
> In the constructor of the same AbstractCrypto (called by
> AbstractCrypto c =
> CryptoFactory.getInstance('org.apache.ws.security.components.crypto.Merlin
> ', (Properties)null), there is this test and comments :
> /*
> * if no properties .. just return an instance, the rest will be
> * done later or this instance is just used to handle certificate
> * conversions in this implementatio
> */
> if (properties == null) {
> return;
> }
>
> Is there a problem with the decryption method when the Crypto have his
> property setting to 'null'?
>
> Thanks for your help, i really don't what can i do to resolve my problem.
> Matthieu
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
