HttpApplication.AuthenticateRequest Event (System.Web)

Switch View :

Classic

Lightweight

ScriptFree

Site Feedback

.NET Framework Class Library

HttpApplication.AuthenticateRequest Event

Occurs when a security module has established the identity of the user.

Namespace: System.Web
Assembly: System.Web (in System.Web.dll)

Syntax

Visual Basic

Public Event AuthenticateRequest As EventHandler

public event EventHandler AuthenticateRequest

Visual C++

public:
 event EventHandler^ AuthenticateRequest {
	void add (EventHandler^ value);
	void remove (EventHandler^ value);
}

member AuthenticateRequest : IEvent<EventHandler,
    EventArgs>

Remarks

The AuthenticateRequest event signals that the configured authentication mechanism has authenticated the current request. Subscribing to the AuthenticateRequest event ensures that the request will be authenticated before processing the attached module or event handler.

For more information about how to handle events, see Consuming Events.

Version Information

.NET Framework

Supported in: 4, 3.5, 3.0, 2.0, 1.1, 1.0

Platforms

Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Reference

HttpApplication Class

System.Web Namespace

PostAuthenticateRequest

Community Content

sisdog

Confusing Description

The description at the top "Occurs when a security module has established the identify of the user" is very misleading. When an HttpModule handles the AuthenticateRequest event its job is to do the authentication. This statement makes it sound as if the AuthenticateRequest event happens "AFTER" authentication. From my understanding, this is not true. If a developer creates a custom IHttpModule and plugs into this event it may have this "APPEARANCE" but it's more due to the fact that a developer's custom HttpModule just happens to be called after the built-in FormsAuthenticationModule has also responded to the event. So, the event itself is "DURING" the authentication but because there are two iHttpModule classes listening to that event, the built in FormsAuthenticationModule gets first crack at the event before the developer's custom HttpModule get to respond.