I agree. In most cases, expecting properties files on the server for this data seems impractical. I overcame this by constructing and using a Properties object at run time from the related data.

So, you can write a simple function to convert the data that you have to a Properties object:

E.g.

public Properties getProperties() {
        Properties props = new Properties();
        props.put("org.apache.ws.security.crypto.merlin.keystore.type", typeString);
        props.put("org.apache.ws.security.crypto.merlin.keystore.password", passwordString);
        props.put("org.apache.ws.security.crypto.merlin.file", fileNameString);

        return props;
}

Then, use the Properties object to construct the Crypto object instance that you typically need for most security/access-related API:

Properties props = getProperties();
Crypto _crypto =
   CryptoFactory.getInstance("org.apache.ws.security.components.crypto.Merlin", props);

// proceed to actual access/security logic using _crypto

Hope this helps,
-Arun

On 10/7/05, Christopher S. Johnson <[EMAIL PROTECTED]> wrote:
I'm trying to programmatically sign soap messages using the _setProperty()
procedure as described on the wss4j web page
(http://ws.apache.org/wss4j/axis.html).  Setting the properties seems to
be fairly easy but I've come across a stumbling block.  It seems simple
enough to pass in the 'signaturePropFile' value yet my clients wont have a
anything like a crypto.properties file but I will know everything that
should be in the crypto.properties file in memory, I'll have a in memory
keystore, password and know the keystore type.  How do I pass the in
memory crypto.properties to wss4j?

Thanks

--
Chris Johnson
[EMAIL PROTECTED]

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


Reply via email to