Hi Tim,

IMHO right now the user cannot provide a java.util.Propertis object as
the crypto properties and the user _must_ specify properties file, if
you are using the standard WSDoAll* handlers.

Also if you don't want to use a keystore, then you will have to
implement the org.apache.ws.security.components.crypto.Crypto impl and
you _must_ specify the implementation class name in it as the value of
the property "org.apache.ws.security.crypto.provider" in the
properties file mentioned above.
You can also consider implementing this in such a way that it can get
the configurations it needs at the run time (may be using a static
thread local hook to change the config params when required).

Thanks,
Ruchith



On 5/2/06, Tim K. (Gmane) <[EMAIL PROTECTED]> wrote:

Hello -

I'm trying to use WSS4J's encryption & signature in Axis. The goal is to
use its configuration files as much as possible. I got UsernameToken
working so far and I'm trying to add encryption + signature.

The problem is that I can't seem to figure out a way to specify the
properties in crypto.properties in a programmatic way. I do not have a
static location for the keystore file location, it is known only at
runtime and it may be different for different users.

Is there a way to provide a Properties object that I can create at runtime
instead of crypto.properties file? Or is there a way to be asked for the
keys via a Callback handler rather than have WSS4J look in the keystore?
That would work too, but I would like to stay away from writing my own
Axis handlers and doing encryption and signature programmatically in the
handlers, I'd like to use the existing handlers and configuration files.

Or maybe I need to extend the Merlin class and add the properties
programmatically when my class is constructed?

What is the key solution, please?

thank you

--
Tim


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to