Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Here is a check list for using ASP.NET Forms Authentication on IIS6</p> <p><strong>Configure IIS:</strong></p> <p>In IIS, Site Properties -> Directory Security -> Authentication and Access Control</p> <ul> <li>Enable Anonymous Access </li> <li>Disable all <em>Authenticated access methods</em> </li> </ul> <p><img src="https://i.stack.imgur.com/cNvqq.png" alt="enter image description here"></p> <p><strong>Configure Forms Authentication:</strong></p> <p>Configure Forms Authentication in your site's <code>web.config</code>:</p> <pre><code>&lt;authentication mode="Forms"&gt; &lt;forms name="MySite" path="/" loginUrl="~/logon.aspx" protection="All" timeout="30" slidingExpiration="true" /&gt; &lt;/authentication&gt; </code></pre> <p>Your <code>name</code> and <code>loginUrl</code> may vary. The <code>slidigExpiration</code> attribute is used to keep extending the forms authentication cookie lifetime rather than just kicking the user off of the site after the <code>timeout</code> has expired. The <code>timeout</code> value is in minutes.</p> <p><strong>Configure Session Timeout:</strong></p> <p>You need to configure your session state <code>timeout</code> to be longer than your Forms Authentication ticket expiry. If you don't do this then an idle session can time out the session but leave the user logged in. Code that expects Session values to be present will throw exceptions because they are gone even though they are still authenticated. The <code>timeout</code> value is also in minutes.</p> <pre><code>&lt;sessionState mode="InProc" timeout="40" /&gt; </code></pre>
 

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