Skip to main content

ASP.NET Membership



ASP.NET Membership

Login Controls:
          ASP.NET simplifies the user creation and management process by providing the following Login controls:

  1. Login
Provides UI. Provides Authentication Code. Implement Authenticate Event for custom user authentication.
  1. LoginView
Display info in it for authenticated users.
  1. LoginStatus
Logout for Authenticated users and Login link for unauthenticated users.
  1. LoginName
Display name of authenticated user.
  1. PasswordRecovery
Password retrieval by sending email or asking Secret Q/A.
  1. CreateUserWizard
  2. ChangePassword

Additionally one can place ValidationSummary control on page for detailed error reporting.

System.Web.Security.Membership class:

Membership class provides the following methods:
CreateUser, DeleteUser, FindUserByEmail, FindUserByName, GeneratePassword, GetAllUsers, GetNumberOfUsersOnline, GetUser, GetUserNameByEmail, UpdateUser, ValidateUser.


System.Web.Security.Roles class:

RoleManagement consist of a set of classes and interfaces that establish role for the current user and manage role information.

Roles class provides the following methods:

AddUserToRole, AddUserToRoles, AddUsersToRole, and AddUsersToRoles.
CreateRole, DeleteRole, FindUsersInRole, GetAllRoles, GetRolesForUser, IsUserInRole.
RemoveUserFromRole, RemoveUsersFromRole, RemoveUserFromRoles, RemoveUsersFromRoles.
Roles class can’t be used for Active Directory or windows account and roles.

Configuring Web Applications to Use ASP.NET Membership:
Select Web Site | ASP.Net Configuration. Login Page must be named Login.aspx
Labels:

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...
Continue Reading »

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...
Post a Comment
Continue Reading »