EasyHostingASP.NET | Best and cheap ASP.NET Hosting in India. This step-by-step article describes how to implement Windows authentication and authorization in an ASP.NET application. To use the built in security of Windows and ASP.NET, implement Windows authentication and authorization on groups and users. To use Windows authentication, you must adjust settings in both Microsoft Internet Information Services (IIS) and the ASP.NET application Web.config file.
- Microsoft Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, or Windows XP Professional
- Microsoft .NET Framework
- Microsoft Internet Information Services (IIS)
- Microsoft Visual Studio .NET
Authentication and authorization
Windows authentication and Windows authorization are two terms that are frequently interchanged. However, they do not have the same meaning. Windows authentication permits the recipient to determine the user’s identity. Windows authorization determines the resources to which a user may gain access.
Configure Web application for Windows authentication
To configure your Web application for Windows authentication, follow these steps:
- Create an ASP.NET Web Application named ASPNETWinAuth. By default, theWebForm1.aspx file appears.
- In the HTML view of WebForm1.aspx, replace the existing code with the following sample code:
- Click Start, point to Programs, point to Administrative tools, and then click Internet Information Services.
- The Internet Information Services MMC appears. Expand Computer, and then expand a Web site that uses Windows authentication.
- Click the ASPNETWinAuth Web site application.
- On the Action menu, click Properties.
- In Properties, click the Directory Security tab.
- Under Anonymous access and authentication control, click Edit.
- In Authentication Methods, click to select Integrated Windows authentication. Click to clear all other check boxes.
- Click OK.
- In Properties, click OK. The ASPNETWinAuth Web application is now configured to accept valid user accounts.
Configure the ASP.NET application
After you configure the IIS Web site for Integrated Windows Authentication, you must configure the ASP.NET application to recognize authenticated users. To do this, you must change the Web.config file. In the Web.config file, locate the <authentication> tag, and then set the mode attribute to Windows, as in the following example:
<authentication mode=”Windows” />
To test your Windows authentication setting, follow these steps:
- In Microsoft Internet Explorer, view the WebForm1.aspx page. This page is located in the Http://Localhost folder. For example:
- Because Integrated Windows Authentication uses the current Windows user information on the client computer for the authentication, it does not immediately prompt the user for a user name and password. However, if the authentication exchange cannot identify the user, a dialog box appears that prompts the user for a Windows user account user name and password.
- Type a valid user name and password. When the page loads, your user name appears in the following format:
Domain Name\User Name
In ASP.NET, you set authorization to the application by adding settings in the Web.config file. You can specify which users or groups are permitted to have access to what resources as follows:
To permit all users of an NT Group named Managers to have access to your resources, use the following code:
<allow roles="domainname\Managers" />
<deny users="*" />
To permit only specific users to have access, use the following code:
<allow users="domainname\user1,domainname\user2,domainname\user3" />
<deny users="*" />
Note You can specify multiple roles or users by using a comma separated list. Verify that you use the correct case when you specify the configuration file element and the associated attribute values. This code is case sensitive.
Best and Cheap ASP.NET Hosting in India Click Here !
- ASPHostPortal vs Site5 – Best Windows ASP.NET Hosting Comparison - September 29, 2017
- Best , Cheap Umbraco 7.7.1 Hosting Recommendation - September 28, 2017
- ASP.NET Web Forms Connection Resiliency and Command Interception - September 27, 2017