Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I'm pretty sure that your code is going to allow access to everybody once a single person logs in - probably not what you want.</p> <p>According to <a href="http://msdn.microsoft.com/en-us/library/ms178473.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms178473.aspx</a>:</p> <p>"Called when the first resource (such as a page) in an ASP.NET application is requested. The <strong>Application_Start</strong> method is <strong>called only one time</strong> during the life cycle of an application"</p> <p>Furthermore according to <a href="http://support.microsoft.com/kb/307598#1" rel="nofollow noreferrer">http://support.microsoft.com/kb/307598#1</a> "Application state variables are, in effect, global variables for each ASP.NET application."</p> <p>I would suggest you use the built in Membership API and restrict access using the web.config files.</p> <p>If you are open to using the Membership API rather than rolling your own authentication mechanism, you can use the web.config to check if a user is authorized for a particular folder. You can also relatively simply have the user log in on one site and automatically be logged into the other sites by sharing authentication tickets -- provided they are all on the same root domain.</p> <p>For sharing authentication tickets see: <a href="http://msdn.microsoft.com/en-us/library/ms998288.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms998288.aspx</a> and <a href="http://www.netomatix.com/development/singlesignon.aspx" rel="nofollow noreferrer">http://www.netomatix.com/development/singlesignon.aspx</a></p> <p>For how to use the web.config to restrict access: <a href="http://www.devhood.com/Tutorials/tutorial_details.aspx?tutorial_id=85" rel="nofollow noreferrer">http://www.devhood.com/Tutorials/tutorial_details.aspx?tutorial_id=85</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload