asp.net - What is the most unobtrusive way to add a layer of security for a private beta of website? -
Suppose I have an ASP.NET site (in this case MVC) which uses form authentication and a specific membership system. The site allows both certified and anonymous users.
When I leave the site as a private beta, I want to add another layer of security at the top of the application, just like a simple password system, for example. Once the user has crossed this layer of protection, I still want my form authentication / subscription system so that the Beta tester can see the site as a certified or anonymous user.
What is the easiest way to achieve this? I'm looking for the easiest solution for which at least new or modified code will be required. Like I do not want to modify every controller to check a particular cookie. There should be a better method ...
There is a question here, but it seems that the site in question (once public) will only serve anonymous requests, so it is not necessary from my situation. Suggestions that serverfault has used some cookie system, but there is no other information about how it has been implemented.
Implement security at the server level in IIS and the account in Active Directory of Windows running on IIS server Add / password.
You will not need to change any code.