Integrated mode means that the pipeline events of ASP. NET run at the same time as the IIS pipeline, what it means is that: 1) In Classic Mode - AuthenticateRequest in ASP. NET runs way after IIS already did the authentication (using Windows auth maybe or basic, etc) and so you will get the User Identity set to it.2) In IntegratedMode - AuthenticateRequest will run at the "same time" in both which will cause it to have a null there.
You should consider using PostAuthenticateRequest if you want to reliably get a User Identity (of course provided you have an authentication module enabled).
Our code relies on checking the Context.User. Identity value in the Global. Asax Application_AuthenticateRequest(...) method to retrieve some information about the logged in user.
This works fine in classic mode but when I flip IIS to use the Integrated Pipeline "Context. User" comes back as null, but only intermittently. Any ideas why?
I have and only Windows Auth enabled in the Virtual Directory.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.