B
Brad Coble
First, please forgive me I'm new here. This question may already have been
answered. I have a Win2K3 server running IIS6 only on our intranet. My plan
was to use our domain to authenticate users.
Here is what I set in web.config:
<authentication mode="Windows"/>
<roleManager enabled="true" defaultProvider="WindowsProvider">
<providers>
<clear/>
<add name="WindowsProvider"
type="System.Web.Security.WindowsTokenRoleProvider"/>
</providers>
</roleManager>
<authorization>
<deny users="?"/>
</authorization>
And under locations
<location path="mx">
<system.web>
<authorization>
<allow roles="automation"/>
<deny users="*"/>
</authorization>
</system.web>
</location>
My expectations for this setup is that all authenticated users(logged in via
our domain) can get to all pages except those that are setup under location.
It works ok except that sometimes, not always, when a user browses to a page
it doesnt like their authentication and forces a request for credentials.
Any ideas why? Thanks!!
Brad Coble
answered. I have a Win2K3 server running IIS6 only on our intranet. My plan
was to use our domain to authenticate users.
Here is what I set in web.config:
<authentication mode="Windows"/>
<roleManager enabled="true" defaultProvider="WindowsProvider">
<providers>
<clear/>
<add name="WindowsProvider"
type="System.Web.Security.WindowsTokenRoleProvider"/>
</providers>
</roleManager>
<authorization>
<deny users="?"/>
</authorization>
And under locations
<location path="mx">
<system.web>
<authorization>
<allow roles="automation"/>
<deny users="*"/>
</authorization>
</system.web>
</location>
My expectations for this setup is that all authenticated users(logged in via
our domain) can get to all pages except those that are setup under location.
It works ok except that sometimes, not always, when a user browses to a page
it doesnt like their authentication and forces a request for credentials.
Any ideas why? Thanks!!
Brad Coble