Assuming you're developing in asp.net and depending on the structure of you
application, what you could do is:
Configuring IIS to access both anonymous and IWA at the top of your site.
Place minimal code in the root of the site (default.aspx plus dependencies)
create one virtual directory for authenticated and place specific code there
create one virtual directory for anonymous and do the same
Note: I assume you can also put the same code and just use vdir point to the
same physical dir and then use IsAuthenticated condition to change the
functions/display accordingly.
Additionally, change the security on the vdirs: one IWA only the second
anonymous only. Make sur IUSR user can access all pages and dependencies.
In the web.config, use strcture authorization thanks to the location tag and
<allow users="?" /> for the root and the anonymous vdir <deny users="?" />
for the authenticated user vdir.
Hope it helps
Marc
Note: I suppose this works with Asp.Net prior 2.0 but never tested.
Note2: I don't think Impersonation could play any role in this case
"BubbaThree" <BubbaThree.RemoveThis@discussions.microsoft.com> wrote in message
news:B137B587-1E1D-43B0-967F-DA6579C28170@microsoft.com...
> I am developing a web application using Visual Studio 2008. The Web
> server
> is Window 2005 v5.00.2195 Service Pack 4. I am using Windows
> Authentication
> with impersonation set to TRUE. This works fine for the majority of the
> users, but some of this information is "public". But on our corporate
> network their are a few workstations that are not domain authenticated. I
> would like for those users to connect via a low priviledged read-only
> common
> account, with out the users having to login.
>
> Is there are way to use Windows Authentication for domain users and
> "anonymous" for users not logged in.
>> Stay informed about: ?? Mixed mode Authentification ??