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]