ASP.NET

1. ASP.NET Introduction 2. Comp of .Net Framework 3.5 3. Sys.Req for VS 2008 4. ASP.NET Envrmnt Setup 5. VS2010 Ultimate Sys.Req 6. Installing VS 2010 7. VS 2012 Sys.Req 8. Installing VS Exp 2012 9. Start the VS 2008 10. Application Life Cycle 11. Page Life Cycle 12. Page Life Cycle Events 13. ASP.NET Example 14. Event Handling 15. Default Events 16. Server Side 17. Request Object 18. Response Object 19. Server Controls 20. Server Controls Properties 21. Server Controls Methods 22. HTML Server Controls 23. Client Side 24. ASP.NET Basic Controls 25. TextBox Control 26. CheckBox Controls 27. RadioButton Controls 28. ListBox Control 29. HyperLink Control 30. Image Control 31. BulletedList Control 32. ASP.NET Directives 33. Implements Directive 34. Master Type Directive 35. Page Directive 36. PreviousPage Type 37. Managing State 38. Control State 39. Cookies 40. Query Strings 41. Server-Side State 42. Session State 43. Validation Controls 44. Required FieldValidator 45. Range Validator 46. Compare Validator 47. RegularExpressionValidator 48. Custom Validator 49. Validation Summary 50. Data Source Control 51. AdRotator Control 52. Calendar Control 53. Calendar Control Example 54. Panel Control 55. Panel Control Example 56. Multi Views Control 57. MultiView & View controls 58. MultiView Control Example 59. FileUpload Control 60. FileUpload Control Eg 61. AJAX Control 62. UpdatePanel control 63. UpdateProgress Control 64. Custom Controls 65. Custom Control Eg 66. Personalization 67. Create Simple Profile 68. ADO.NET 69. ADO.NET Objects 70. DataTable 71. DataRow 72. DataColumn 73. Object Example 74. Error Handling 75. Tracing Errors 76. Debugger 77. Security 78. Authentication 79. Authorization 80. LINQ 81. LINQ Query Operators 82. LINQ Example 83. Caching 84. Data Caching 85. Output Caching 86. Object Caching 87. Web Services 88. Create Web Services Eg 89. Web & Machine.config 90. Settings Schema 91. ASP.NET Deployment 92. XCopy Deployment 93. Web Setup Project 94. ASP Interview Part 1 95. ASP Interview Part 2 96. ASP Interview Part 3 97. ASP Interview Part 4 98. ASP Interview Part 5 99. ASP Interview Part 6
Pr.Pg Next Pg

Authentication tutorials

  • Authentication is the process by which you obtain identification credentials such as the user's name and password and validate those credentials against some authority.

  • An ASP.NET Web application can be provided with one of the following types of security:

  • WindowsAuthintication: The application is secured by using Integrated Windows Authentication. In this method, access to a Web application is allowed only to those users who are able to verify their Windows credentials.Credentials can be verified against the Windows authentication database (SAM) or against Active Directory.

  • Passport Authintication: The application is secured by using Microsoft Passport authentication. Passport is a single-sign-on technology developed by Microsoft for use on the Web. Typically, Passport authentication is used when you need single log on capability across multiple domains.

  • Forms Authintication: ASP.NET includes a built-in feature, called forms-based authentication, which can be used to implement customized logic for authenticating users and authentication handlers without having to worry about session management using cookies. In forms-based authentication, when a user is determined to be unauthenticated, the user is automatically redirected to the login page. Some of the benefits of the forms-basedauthentication are the following:

    1. Developers can configure forms-based authentication for various parts of the Web site differently, because the Web.config file is a hierarchical XML document.

    2. Administrators and developers can change the authentication scheme quickly and easily in the Web.config file.

    3. Administration is centralized because all the authentication entries are in one place the Web.config file.

    4. Set the Authentication mode to "Forms" in the Web.config file. This file should be present in the same directory as the ASP.NET Web application.

<configuration>

<system.web>

<authentication mode="Forms">

 

<!-- Assign a cookie named B2CBuySiteAuthCookie when user is authenticated. The page used for validating user credentials is userlogin.aspx. Make sure the cookie is encrypted and validated by setting the protection to All, the cookie will timeout after 10 minutes -->

 

<forms name=".B2CBuySiteAuthCookie" loginUrl= "userlogin.aspx" protection="All" timeout="10" />

</authentication>

<authorization>

<!-- anonymous users will be denied access.

This is needed to force forms-authentication -->

.<deny users="?"/>

</authorization>

</system.web>

</configuration>

None/Default Authintication: Default authentication is used when you do not want any security on your Web application; anonymous access is required for this security provider. Among all authentication providers, Default authentication provides maximum performance for your application. This authentication provider is also used when you use your own custom security.

 

Pr.Pg border                                              Next Pg