Scenario - a developer wants to restrict unauthorized access to a we service in his application.
WARNING: This method is easy but not bulletproof !!!!
The level of security desired is modest and the developer does NOT want to use SSL, WS-* extensions or any other certificate based infrastructure.
A customer emailed be this week with this very question.
They were using the ASP.NET Membership Application Service and Forms based authentication in their application and discovered that the user's authenticated state in the application was not accessible from his web services.
The problem ?
Web Services (ASMX) and Web Pages (ASPX) can both have session state but they do not SHARE session state.
Here are two quick ways to authenticate calls to Web Service Methods. (There are, of course, many ways.)
First...
You can pass the UserName and Password to the web service me ...
Go to the complete details ...