Hi Senaka, I saw this email after the one I just responded to. That would be great if you have any code samples or let me know how to get at the http header. Our web services allow simple authentication as arguments, http basic auth, or WS-SECURITY. So I will definately be using the Rampart/C code as well.
I also will need to mess around with stuff in the SOAP envelope and headers as we have some other custom stuff implemented in gsoap that embeds some XML with other authentication info. So I will need to find out how to process things at a lower level on both input and output for the server code. Thanks, -Dave. -----Original Message----- From: Senaka Fernando [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 9:13 PM To: Apache AXIS C Developers List Subject: Re: [AXIS2C] HTTP Basic Authentication question Hi Dave, Do you mean access to Authentication info on the server side? Well that is not implemented as yet. However, you may be able to access the Auth Header and make use of the Basic Authentication Credentials. I will look into this and let you know. We did not focus on server side Authentication as we do have WS-Security support, Rampart/C, which can provide you the ability to handle this, and many other security related scenarios. You can find more info on Rampart/C at [1]. [1] http://ws.apache.org/rampart/c/ Regards, Senaka > Hi All, > > With my gsoap web services I can get at the userid and password that > are passed in the HTTP header using HTTP Basic Authentication. It > decodes the password as well and sticks both the userid and password > in the structure that it passes to me. > > I want to offer the same support with my Axis2/C implementation. Does > the Axis2/C code do something similar to the above? I'm basically > just wanting to get a userid and password passed via HTTP Basic auth > and use these credentials in my code to log the user in. > > Thanks, > > -Dave. > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they are addressed. > Any unauthorized review, use, disclosure or distribution is > prohibited. If you are not the intended recipient, please contact the > sender by reply e-mail and destroy all copies of the original message. > ********************************************************************** > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
