Home/ Questions/Q 297721
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T06:39:56+00:00

I’ve built ASP.NET Web Services in the past that either were publicly consumed, or

  • 0

I’ve built ASP.NET Web Services in the past that either were publicly consumed, or used Windows Authentication. I now need to build a Web Service that uses the SOAP 1.1 protocol and it needs to be secured with a username and password from the caller.

It seems setting up the infrastructure for WCP is overkill for one or two Web Services. Any other suggestions? I was also thinking of using ASP.NET 4.0 Beta, if anyone has explored that for this scenario, it would be helpful to know your opinion.

Thanks in advance for your suggestions.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The simple way is to create a special header that carries the auth info for every call and authenticate/authorize the user that way

    Here’s some sample code:
    http://aspalliance.com/805_Soap_Headers_Authentication_in_Web_Services

    Note that in this way you are sending clear text username and password so you would want to use ssl or use some kind of digest authentication

    • 0