i
Web Application Fundamentals
Using Internet Information Services
Web Forms
ASP.NET MVC
Web Services
ASP.NET Features
Request/Response Programming
HttpRequest Class
HTTP Collections
HttpResponse Class
Redirection
HttpUtility Class
Using Visual Web Developer
Visual Studio Forms Designer
Using Components
Shadow Copying
Using the Global.asax File
Data Binding
Different Types Of Caching
How to use Object cache
Optimizing Your ASP.NET Application
What Is Caching [Storage]
Forms Authentication
Windows Authentication
ASP.NET Security Fundamentals
Data Source Controls
SqlDataSource
SiteMapDataSource
The AccessDataSource Control
ObjectDataSource
Connection String Storage
GridView
DetailsView
FormView
ListView
DataPager
Entity Data Model
EntityDataSource
Remote Method Calls
Ajax Control Toolkit
Ajax Client Library
Rich Client Applications
Ajax [Asynchronous JavaScript and XML]
ScriptManager
UpdatePanel
Model-View-Controller Pattern
ASP.NET MVC versus Web Forms
ASP.NET MVC Projects in Visual Studio
Action Methods in MVC
Routing in MVC
Strongly-Typed Views [Add images here from the visual studio]
Model Binding
Validation
ADO.NET [ActiveX Data Object]
ASP.NET Data Providers
Connections
Commands
DataReaders and Connected Access
DataSets and Disconnected Access
If you are creating an application only for a limited number of people who are part of a network domain, then Windows Authentication is the best choice. Users are authenticated against the identity store such as Active Directory, and the credentials are not transmitted across the Internet.
For enabling the windows authentication, we need to add below key in the web.config file.
Windows authentication helps when the user using the application that belongs to the same organization and also the applications method validate the user by using the credentials stored in the windows domain.
Authorization:
Authorization means providing the approval to access the requested resource. The resource may be like the web page, image, any file, etc. After the user is authenticated, then the Authorization comes in the picture.
If different users need to have different privileges, then impersonation in ASP.net configuration files needs to be turned on. That can achieve with the help of below:
Syntax:
If we are allowing anonymous access, ASP.NET takes the identity from IIS. If we are allowing anonymous access, this means ASP.NET will impersonate the IUSR_ComputerName account.
If we are not allowing anonymous access, ASP.NET takes the credentials of the authenticated user and makes requests for resources. Thus by turning on the impersonation and using the non-anonymous method of authentication in IIS.
We can let users log on and use their identities within your ASP.NET application.
With the above setting, all the requests are made as to the specified user.
Ex -
We can authenticate the user for a single application and use that user's identity every time someone authenticates to the application.
Don't miss out!