Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

IIS complaining about Identity Impersonation using LDAP Authentication

Tags:

I followed a tutorial to implement LDAP authentication in an ASP.NET/C# 4.0 web application. I did so in Visual Studio 2010. The site runs fine in debug mode through Visual Studio, but when I publish this site in IIS7, it is failing with the following error:

HTTP Error 500.24 - Internal Server Error An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

Most likely causes:

  • system.web/identity@impersonate is set to true.

In fact, part of the tutorial required that I add this to the config file...

<identity impersonate="true"/>

So why would I be getting this error and how do I fix it?

like image 279
Jerry Dodge Avatar asked Dec 10 '12 16:12

Jerry Dodge


People also ask

How do I disable impersonation in IIS?

Use Internet Information Services (IIS) Manager to disable anonymous authentication for the application and enable integrated windows authentication. In the application's Web. config file, set the impersonate attribute in the identity element to true.

How do I fix system Web identity impersonate is set to true?

web/identity@impersonate is set to true. Things you can try: If the application supports it, disable client impersonation. If you are certain that it is OK to ignore this error, it can be disabled by setting system.

How do I enable impersonation in IIS?

ASP.NET Impersonation AuthenticationOpen IIS Manager and navigate to the level you want to manage. In Features View, double-click Authentication. On the Authentication page, select ASP.NET Impersonation. In the Actions pane, click Enable to use ASP.NET Impersonation authentication with the default settings.


1 Answers

Try changing your application pool's pipeline mode to 'Classic'

You do this by opening IIS -> Application Pools -> Right-click your application pool and select Basic Settings -> Managed pipline mode, change to Classic

Restart your app pool and site (shouldn't need to but never hurts to try) and try again.

Another thing you can try, instead of the above, is to put the following in your web.config file, inside the <system.webServer> node:

       <validation validateIntegratedModeConfiguration="false" />
like image 173
Darren Wainwright Avatar answered Sep 29 '22 12:09

Darren Wainwright