|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
ASP.NET Login Controls Overview
The ASP.NET login controls work together to provide for your ASP.NET Web applications a robust login solution that requires no programming. By default, login controls integrate with ASP.NET membership and forms authentication to help automate user authentication for your Web site. For information about using ASP.NET membership with forms authentication, see.
By default, the ASP.NET login controls work in plain text over HTTP. If you are concerned about security, use HTTPS with SSL encryption. For more information on SSL, see Configuring SSL on a Web Server or a Web Site in the IIS documentation.
Login controls might not function properly if theof the ASP.NET Web page is changed from POST (the default) to GET.
This topic describes each ASP.NET login control and provides links to the control's reference documentation.
Thecontrol displays a user interface for user authentication. The Login control contains text boxes for the user name and password and a check box that allows users to indicate whether they want the server to store their identity using ASP.NET membership and automatically be authenticated the next time they visit the site.
The Login control has properties for customized display, for customized messages, and for links to other pages where users can change their password or recover a forgotten password. The Login control can be used as a standalone control on a main or home page, or you can use it on a dedicated login page.
If you use the Login control with ASP.NET membership, you do not need to write code to perform authentication. However, if you want to create your own authentication logic, you can handle the Login control'sevent and add custom authentication code.
Thecontrol allows you to display different information to anonymous and logged-in users. The control displays one of two templates: the or the . In the templates, you can add markup and controls that display information appropriate for anonymous users and authenticated users, respectively.
The LoginView control also includes events forand , which allow you to write handlers for when the user logs in and changes status.
Thecontrol displays a login link for users who are not authenticated and a logout link for users who are authenticated. The login link takes the user to a login page. The logout link resets the current user's identity to be an anonymous user.
You can customize the appearance of the LoginStatus control by setting theand properties.
Thecontrol allows user passwords to be retrieved based on the e-mail address that was used when the account was created. The PasswordRecovery control sends an e-mail message containing a password to the user.
You can configure ASP.NET membership to store passwords using non-reversible encryption. In that case, the PasswordRecovery control generates a new password instead of sending the original password to the user.
You can also configure membership to include a security question that the user must answer to recover a password. If you do, the PasswordRecovery control asks the question and checks the answer before recovering the password.
The PasswordRecovery control requires that your application can forward e-mail message to a Simple Mail Transfer Protocol (SMTP) server. You can customize the text and format of the e-mail message sent to the user by setting theproperty.
Password information sent in an e-mail message is sent as clear text.
The following example shows a PasswordRecovery control declared in an ASP.NET page with MailDefinition property settings to customize the e-mail message.
<asp:PasswordRecovery ID="PasswordRecovery1" Runat="server" SubmitButtonText="Get Password" SubmitButtonType="Link"> <MailDefinition From="administrator@Contoso.com" Subject="Your new password" BodyFileName="PasswordMail.txt" /> </asp:PasswordRecovery>
Thecontrol collects information from potential users. By default, the CreateUserWizard control adds the new user to the ASP.NET membership system.
The CreateUserWizard control gathers the following user information:
Confirmation of password
This information is used to authenticate users and recover user passwords, if necessary.
The CreateUserWizard control is inherited from thecontrol.
The following example shows a typical ASP.NET declaration for the CreateUserWizard control:
<asp:CreateUserWizard ID="CreateUserWizard1" Runat="server" ContinueDestinationPageUrl="~/Default.aspx"> <WizardSteps> <asp:CreateUserWizardStep Runat="server" Title="Sign Up for Your New Account"> </asp:CreateUserWizardStep> <asp:CompleteWizardStep Runat="server" Title="Complete"> </asp:CompleteWizardStep> </WizardSteps> </asp:CreateUserWizard>
Thecontrol allows users to change their password. The user must first supply the original password and then create and confirm the new password. If the original password is correct, the user password is changed to the new password. The control also includes support for sending an e-mail message about the new password.
The ChangePassword control includes two templated views that are displayed to the user. The first is the, which displays the user interface used to gather the data required to change the user password. The second template is the , which defines the user interface that is displayed after a user password has been successfully changed.
The ChangePassword control works with authenticated and non-authenticated users. If a user has not been authenticated, the control prompts the user for a login name. If the user is authenticated, the control populates the text box with the user's login name.