Authentication and Authorization in ASP.NET
Note: This article was originally published on AspAlliance
By: Joydip Kanjilal
Date: October 28, 2007
Authentication is the process of determining the authenticity of a user based on the user's credentials. Whenever a user logs on to an application, the user is
first authenticated and then authorized. The application's web.config file contains all of the configuration settings for an ASP.NET application. It is the job
of the authentication provider to verify the credentials of the user and decide whether a particular request should be considered authenticated or not. An
authentication provider is used to prove the identity of the users in a system. ASP.NET provides three ways to authenticate a user:
- Forms authentication
- Windows authentication
- Passport authentication
Hence, ASP.NET contains the three respective authentication providers to support the above authentication modes.
This authentication mode is based on cookies where the user name and the password are stored either in a text file or the database. After a user is authenticated,
the user's credentials are stored in a cookie for use in that session. When the user has not logged in and requests for a page that is insecure, he or she is
redirected to the login page of the application. Forms authentication supports both session and persistent cookies. Authentication modes can be specified in the
application's web.config file as shown below:
The following needs to be specified in the application's web.config file for using Forms Based Authentication in ASP.NET:
Note: The statement <deny users="?"> in the web.config file as stated in Listing 2 implies that all permissions are
granted only to the authenticated users. The users who are not authenticated are not granted any permission. The symbol "?" indicates all Non
Authenticated and Anonymous users.
Generally the user's credentials are stored in the database and the entered credentials are verified using those that are stored in the database. Typically, the
user enters the username and the password, clicks the login button and the form validates the values against values from the database. This is shown in the code
The static method RedirectFromLoginPage creates an authentication ticket and is used to redirect an authenticated user back to the originally requested URL or the
default URL. The authentication ticket creates a persistent cookie that becomes a part of the HttpResponse object. Later, when the user tries to access a page in
a restricted folder, the ASP.NET framework uses the cookie to retrieve the ticket and determine whether the user has access to that particular resource. The first
parameter to this method identifies the user while the second is used to specify whether the user's authentication cookie needs to be persisted across multiple
The user's credentials can be also be specified in the web.config file as shown below:
This is the default authentication mode in ASP.NET. Using this mode, a user is authenticated based on his/her Windows account. Windows Authentication can be used
only in an intranet environment where the administrator has full control over the users in the network. The following should be set in the web.config file to use
Note: The symbol "*" indicates all users inclusive of Authenticated and Anonymous users. Hence the statement <allow users = "*"> in
the web.config file as stated in Listing 5 indicates that all permissions are granted to both the Anonymous and Authenticated users.
Windows authentication can be of the following types
- Anonymous Authentication
- Basic Authentication
- Digest Authentication
- Integrated Windows Authentication
Passport authentication is a centralized authentication service that uses Microsoft's Passport Service to authenticate the users of an application. It allows the
users to create a single sign-in name and password to access any site that has implemented the Passport single sign-in (SSI) service. The following code shows how
we can specify Passport Authentication in the web.config file:
ASP.NET also supports custom authentication. In such a case the authentication mode has to be specified as none in the web.config file as shown below:
Then we need to write our own custom authentication provider.
According to MSDN, "When using impersonation, ASP.NET applications can optionally execute with the identity of the client on whose behalf they are operating.
The usual reason for doing this is to avoid dealing with authentication and authorization issues in the ASP.NET application code. Instead, you rely on Microsoft
Internet Information Services (IIS) to authenticate the user and either pass an authenticated token to the ASP.NET application or, if unable to authenticate the
user, pass an unauthenticated token. In either case, the ASP.NET application impersonates whichever token is received if impersonation is enabled. The ASP.NET
application, now impersonating the client, then relies on the settings in the NTFS directories and files to allow it to gain access, or not. Be sure to format
the server file space as NTFS, so that access permissions can be set.
Impersonation is disabled by default and allows the ASP.NET process to act as the authenticated user, or as an arbitrary specified user. Impersonation can be
specified in the web.config file as shown below:
It is also possible to use a particular identity for all authenticated requests. This is possible by specifying the following in the application�s web.config file:
How Authentication and Authorization Works
The following section lists the sequence of events that take place in the authentication and authorization process when a new request arrives.
The IIS first checks the validity of the incoming request. If the authentication mode is anonymous (default) then the request is authenticated automatically. But if
this authentication mode is overridden in the web.config file settings, the IIS performs the specified authentication check first before the request is passed on
Now ASP.NET checks whether Impersonation is enabled or not. If impersonation is enabled, ASP.NET executes with the identity of the entity on behalf of which it is
performing executing the task. If impersonation is not enabled, the application runs with the identity of the IIS local machine's identity and the privileges of the
ASP.NET user account. ASPNET or NETWORK SERVICE is the default ASP.NET unprivileged account on Windows XP and Windows Server 2003, respectively. Now, the identity
that has already been authenticated and verified is used to request resources from the operating system. Then ASP.NET performs an authorization check on the
requested resources and if the user is authorized, it returns the request through IIS.
Application security plays a major role in building robust applications. The application should be able to restrict or limit access to the resources based on the
user's credentials and even disallow access to resources to unauthorized users of the system. This article just gave a basic idea about ASP.NET's in-built
Authentication and Authorization support. Please post your comments and suggestions. Happy reading!