Closed GoogleCodeExporter closed 9 years ago
Original comment by azizatif
on 9 Mar 2009 at 8:30
Does the web.config of the application enforce Windows authentication? Like
this?
<authentication mode="Windows" />
<authorization>
<allow users="*" />
<deny users="?" />
</authorization>
Does adding the above give you a consistent user field when running the
application
from Visual Studio versus under IIS?
Original comment by azizatif
on 9 Mar 2009 at 9:35
Original comment by azizatif
on 9 Mar 2009 at 9:36
adding the above didn't help.
but i got the user field filled by changing iis property from anonymous access
to
integrate windows authentication.
but how do i fill the user field with the logged in username.
Original comment by webqates...@gmail.com
on 10 Mar 2009 at 6:35
Sorry, that was my bad. The <authorization> section should have read:
<authorization>
<deny users="?" />
<allow users="*" />
</authorization>
Anyhow, this issue is not a problem with ELMAH. What you are observing is
simply a
difference of implementation between the ASP.NET Development Server that ships
with
Visual Studio and IIS. The ASP.NET Development Server seems to, by default,
associate
the process user with the request. IIS, on the other hand, associates a user
with the
request only if necessary (due to authorization) and authenticated.
Original comment by azizatif
on 12 Mar 2009 at 10:50
Original comment by azizatif
on 13 May 2009 at 9:07
Original issue reported on code.google.com by
webqates...@gmail.com
on 9 Mar 2009 at 6:54Attachments: