But then, how do we proceed authenticating a client. Let's say we're setting up another web client that will use this service. How then does this user for another web client has access to this web service?
On 8/14/07, Matt Raible <[EMAIL PROTECTED]> wrote: > > In security.xml, add a pattern that protects /services/**. > > Matt > > On 8/13/07, Dale Newfield <[EMAIL PROTECTED]> wrote: > > Matt Raible wrote: > > > The WSDL should be at: > > > > > > http://localhost:8080/services/UserService?wsdl > > > > The question I need to find an answer to (but I can't say I've spent any > > time on it, yet) is how to secure (authenticate) those services? Care > > to give me a free clue? > > > > -Dale > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > http://raibledesigns.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- /fadhli
