Chris,
pls have a look into the javadocs, in particular
WSHandlerConstants.
Some WSDD files can be found in th interop dierctory
and subdirectories thereof. They show the various
interop scenarios.
Regards,
Werner
csj wrote:
> Sorry to be a pain :)
>
> But I found the documentation to be slim on these things, or maybe have
> yet to find the documentation :P
>
> On Tue, 13 Sep 2005, Werner Dittmann wrote:
>
>
>>Well, each client has its own certifcate it uses to sign. The
>>certificate contains the public key to verify the Signature. Either
>>the client puts the certificate directly into the request or refernces
>>the certificate using some identifier. Because nothing is specified in
>>the deployment files thee default is used: Issuer name and
>>serial number to identify the certificate.
>
>
> Where can I find documentation on what can be specified in the deployment
> files ?
>
>
>>Using Issuer / serial number requiers that both parties have the
>>certificate in their keystore. Thus the server needs every client's
>>certificate in the store.
>
>
> How can I tie this into LDAP rather then using keystore files on the
> server ? Say I have 1000+ users, I dont really want be using a keystore
> file.
>
>
>>If you use the direct method (clients includes certificate in request)
>>then the server only needs the certificate of the signing authority
>>(Certificate Authority, CA) to verify the "trust" of the client's
>>certificate.
>
>
> Are there any samples on implementing these methods using WSS4J, such as
> the direct method ?
>
> ..Chris
>
>
>>Regards,
>>Werner
>>
>>
>>csj wrote:
>>
>>>My client side wsdd has the following requestFlow in it.. this works
>>>great, I can sign the message and using the keystore defined in the
>>>crypto.properties file..
>>>
>>><requestFlow>
>>> <handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
>>> <parameter name="user" value="User1"/>
>>> <parameter name="passwordCallbackClass"
>>> value="localhost.axis.services.stock_wss_01.PWCallback"/>
>>> <parameter name="action" value="Signature"/>
>>> <parameter name="signaturePropFile" value="crypto.properties" />
>>> </handler>
>>></requestFlow>
>>>
>>>
>>>Server side, like I said I'm not sure how this should work..
>>>
>>><requestFlow>
>>> <handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
>>> <parameter name="action" value="Signature"/>
>>> <parameter name="signaturePropFile" value="crypto.properties" />
>>> </handler>
>>> </requestFlow>
>>>
>>>This service setup seems to work on both sides where cropyto.properties
>>>points to the same keystore on both ends.
>>>
>>>I'm confused on how the server side knows what public key to use on the
>>>incoming connection to check the signature on the soap message.
>>>
>>>
>>>For this to work with multiple users that each have differnt signing certs
>>>how will the server make this check.
>>>
>>>Thanks
>>>
>>>On Tue, 13 Sep 2005, Ashok Shah wrote:
>>>
>>>
>>>
>>>>Chris,
>>>>
>>>>Could you please show us your deployment files on server side? And on the
>>>>client side.
>>>>
>>>>thnx
>>>>
>>>>--as
>>>>
>>>>On 9/13/05, csj <[EMAIL PROTECTED]> wrote:
>>>>
>>>>
>>>>>Thanks for the reply
>>>>>
>>>>>Maybe I should paint the whole picture better...
>>>>>
>>>>>I have a simple service... lets says the stock service example...
>>>>>
>>>>>Users build soap messages and sign them using their private keys following
>>>>>the WS-Security spec. They then connect to the stock service using
>>>>>mutually authenticated ssl so the server side has complete knowledge on
>>>>>whos connecting by grabbing the ssl context information, thus passing user
>>>>>name and password tokens is not needed. This part works great on my
>>>>>current setup..
>>>>>
>>>>>The sticking point..
>>>>>
>>>>>On the server side I need to add a handler to verify the digital
>>>>>signatures of the messages, this should be done using the clients public
>>>>>key rather then a passwordCallback implementation that requires knowledge
>>>>>of private keys and keystore passwords.
>>>>>
>>>>>Do I have to write this server side handler from scratch parsing the soap
>>>>>messages for the signatures or is there WSS4J hooks or methods I can use
>>>>>the verify the signature digest, obtain the signature, so I can do some
>>>>>kind of LDAP lookup or something, and then convert the message to a
>>>>>"regular" soap message before any security was added so I can do the stock
>>>>>lookup?
>>>>>
>>>>>Any feedback and or examples on this would be great..
>>>>>
>>>>>Thanks
>>>>>..Chris
>>>>>
>>>>>
>>>>>On Tue, 13 Sep 2005, Davide Romanini wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Il giorno lun, 12/09/2005 alle 18.23 -0400, csj ha scritto:
>>>>>>
>>>>>>
>>>>>>>Ashok,
>>>>>>>
>>>>>>>How is the password callback class used on the server side ?
>>>>>>>
>>>>>>>Thanks
>>>>>>>..Chris
>>>>>>>
>>>>>>
>>>>>>Just implement a CallbackHandler that sets the right password for the
>>>>>>user. For certificates the user rapresents the alias in the keystore.
>>>>>>
>>>>>>Example:
>>>>>>
>>>>>>public class PWCallback implements CallbackHandler
>>>>>>{
>>>>>>public void handle(Callback[] c)
>>>>>>{
>>>>>>for(int i = 0; i < c.length; i++)
>>>>>>{
>>>>>>if(c[i] instanceof WSPasswordCallback)
>>>>>>{
>>>>>>WSPasswordCallback pc = (WSPasswordCallback)c[i];
>>>>>>pc.setPassword("mysecretpassword");
>>>>>>}
>>>>>>}
>>>>>>}
>>>>>>}
>>>>>>
>>>>>>You can use pc.getIdentifer() to get the user/alias for which you are
>>>>>
>>>>>setting the password
>>>>>
>>>>>
>>>>>>Regards,
>>>>>>Davide Romanini
>>>>>>
>>>>>>
>>>>>
>>>>>--
>>>>>Chris Johnson
>>>>>[EMAIL PROTECTED]
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>>>For additional commands, e-mail: [EMAIL PROTECTED]
>>>>>
>>>>>
>>>>
>>>>
>>>>--
>>>>Ashok Shah
>>>>
>>>
>>>
>>>--
>>>Chris Johnson
>>>[EMAIL PROTECTED]
>>>
>>>---------------------------------------------------------------------
>>>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]
>>
>>
>
>
> --
> Chris Johnson
> [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> 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]