Apr 04, 2017 02:00 PMfirstname.lastname@example.org|LINK
There are no linked servers involved in the app. I definitely plan on using an AD group to authorize my users, but, for now, I just want to get this working for myself, to verify that I can actually create a web app that uses Windows authentication all
the way through to the backend database (i.e. I don't want users who are already authenticated on our network to have to deal with a login prompt for the app).
You say that I may not need to use the NT User configured for the App Pool Identity, and recommend I put that back to the default. By default, I assume you mean the "ApplicationPoolIdentity" identity. I made that change, and stopped and started the application
pool. I am still getting the "Login failed for user NT AUTHORITY\ANONYMOUS LOGON" error mentioned in the latter portion of my post.
To cloud the issue further, I tried logging on to the server on which I've published the app, and tried accessing it in the browser on that machine (e.g.
http://localhost/AppName). On that side, I get a lengthy error page (I assume because I specified debug="true" in my web.config). The error there is "HTTP Error 500.24 - Internal Server Error An ASP.NET setting has been
detected that does not apply in Integrated managed pipeline mode". None of the suggested fixes on that page are appealing because I want the application to perform client impersonation for connection to the backend database, I've already configured validateIntegratedModeConfiguration="false",
and I don't wish to use an application pool using Classic .NET mode.