User Authentication Without a Logon Window in ASP.NET Web Forms Applications
- 4 minutes to read
This topic details the steps performed from the moment when the WebApplication object has been created and initialized, until the moment an end-user has been authenticated to the application. In accordance with the Authentication Strategy that is used by the Security System in your application, end users can be asked to type credentials in a logon window to be authenticated. There are two built-in Authentication Strategies in XAF. The AuthenticationStandard authenticates end-users with the information typed in the logon window. The AuthenticationActiveDirectory does not require the logon window to be displayed. It takes the required information from the system’s active directory. This topic details how end-users are authenticated when the built-in AuthenticationActiveDirectory strategy is used. You can customize the AuthenticationActiveDirectory so that a logon window is displayed and the information typed in it is used for authentication. In this instance, read the User Authentication using a Logon Window in ASP.NET Web Forms Applications topic to learn how the logon window is displayed.
#Authentication
Stage Description | Ways to Interfere |
---|---|
To start the authentication process, an Object Space is created to check whether or not a record defining the user logging on exists in the application database. Before accessing the database, the compatibility of the module versions in the database and their actual versions is checked. If the versions in the database are greater than the actual ones, an exception is raised, which requires that you increase your application’s version. If lower, the Xaf | Before the authenticating process is started, you can access the Logon You can perform a custom process of checking the database and application compatibility. For this purpose handle the Xaf If you do not need the scenario implemented in the Xaf Use the Xaf |
When the Authentication | If the default authentication performed by a built-in Authentication class does not satisfy your requirements, implement a custom class. For instance, inherit from one of the built-in authentication classes: Authentication |
The end-user customizations layer is created. In XAF ASP. | You can store the customizations made to a List View in the web browser cookies by setting the IModel Handle the Xaf |