eader and a password callback class to authenticate a user making a
> > request. The spec outlines ways to encrypt and sign SOAP messages as well.
> >
> > Greg
> >
> >
> >
> > -Original Message-
> > From: Wagle, Shriniwas [mailto:[EMAIL P
> > From: Wagle, Shriniwas [mailto:[EMAIL PROTECTED]
> > Sent: Friday, October 29, 2004 10:23 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: adding security to webservices in axis
> >
> > We implemented security at the transport level using SSL with
> > client
; Greg
>
>
>
> -Original Message-
> From: Wagle, Shriniwas [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 29, 2004 10:23 AM
> To: [EMAIL PROTECTED]
> Subject: RE: adding security to webservices in axis
>
> We implemented security at the transport level using
request. The spec outlines ways to encrypt and sign SOAP messages as well.
Greg
-Original Message-
From: Wagle, Shriniwas [mailto:[EMAIL PROTECTED]
Sent: Friday, October 29, 2004 10:23 AM
To: [EMAIL PROTECTED]
Subject: RE: adding security to webservices in axis
We implemented security at
We implemented security at the transport level using SSL with
client-authentication.
The good thing about this is the web services code does not have to deal
with security related aspects at all. It works well, and in a
predictable manner.
We had a binary level of security - either a client can in
http://www-128.ibm.com/developerworks/webservices/library/ws-sec1.html
The following article provides good introduction to different options
available to implement security in Tomcat + Axis.
Regards,
Ashutosh
-Original Message-
From: Marco Mistroni [mailto:[EMAIL PROTECTED]
Sent: Thursda
