Is it safe to set validateIntegratedModeConfiguration=false in order to continue using identity impersonate=true?

Question

We have upgraded an ASP.NET web application from IIS6 to IIS7 integrated mode. Our application uses:

<identity impersonate="true"/>

and therefore we have had to set:

<validation validateIntegratedModeConfiguration="false" />

Is this sensible? My instincts say not, but searching on google for this issue, this "workaround" is suggested on every page visited.

Is impersonation no longer a good practice in IIS7 integrated, and should we abandon it and come up with a different solution?

Answer 1

@GregT: Below is the link that answers your question

http://forums.iis.net/t/1150266.aspx
http://mvolo.com/breaking-changes-for-aspnet-20-applications-running-in-integrated-mode-on-iis-70/

As I understand that specific line of code is added up to log issues as errors and perform the necessary operation.