I've set up an ASP.NET MVC application for my company's Intranet that grabs the user's NT creds via System.Web.HttpContext.User and checks against its own database to perform authentication/authorization. This works just fine on my local machine, and I assume it will also work once deployed to the production server, but the development server is on a different domain than the users. While trying to test the app, I get prompted for a username and password, which isn't supposed to happen. Worse, entering my login creds still doesn't work. I'm deploying a MVC 2 application to an IIS 6 server.
The steps I read to take to get Integrated Windows Authentication to work included putting these lines in my Web.config file:
<authentication mode="Windows"/>
<identity impersonate="true"/>
Then, on IIS in Directory Security uncheck the checkbox that allows anonymous authentication, and make certain that only Windows authenti ...
Go to the complete details ...