ASP.NET 2.0 Login Controls and Security Posted by R@hUl | at 9:16 AM

Paul Litwin • Developer ? Focus: ASP.NET, ASP, VB, C#, SQL Server, …? MCSD? Microsoft MVP? Programming Mngr with Fred Hutchinson Cancer Research Center • Co-Founder and Senior Trainer ? Deep Training • www.deeptraining.com • Conference Chair/Speaker ? Chair, Microsoft ASP.NET Connections? Member INETA Speakers Bureau • Author ? Author/co-author of a dozen books, including… • ASP.NET for Developers• Access Cookbook, 2nd edition• Access 2002 Desktop/Enterprise Dev Handbook Slides & Samples Download • You can download them from: ? www.deeptraining.com/litwin Agenda • New Provider-Based APIs• ASP.NET 2.0 Security Highlights• Security Setup Wizard• Login Controls• Membership Service• Role Service New Provider-Based APIs Goal: Reduce code you have to write • Provider-based model ? Defaults to SQL Server Express but also works with SQL Server, Access, and extendable to custom providers (see next few slides for gotcha) • Works with ? Membership? Role Management? Profiles Provisioning Application Database and Un-Hardwiring SQL Express (1 of 3) • Visual Studio 2005 is setup so that SQL Express is the application database(membership, role, & personalization providers)• This is hard-wired in machine.config• You need to perform a few extra steps to use non-express version of SQL Server for the app db in your project Provisioning Application Database and Un-Hardwiring SQL Express (2 of 3) 1. Run aspnet_regsql command-line tool to start ASP.NET SQL Server Setup Wizard a) On 2nd page, select Configure SQL Server for Application Services b) On the next page, specify your database server name and for database (only need to do step #1 once per SQL Server) 2. From Visual Studio, add a new web.config file the site (if it’s not already there) Provisioning Application Database and Un-Hardwiring SQL Express (3 of 3) 3. Replace the empty element with (for example if SQL Server is on localhost): Note: unless you plan on tweaking the machine.config orcreating a new provider you need to stick with the Local Sql Server name which the Asp Net Sql Profile Provider is expecting to see. 2.0 Security Highlights (1 of 2) • Forms Authentication ? Cookieless authentication now supported • Login Controls ? UI controls for managing login of users • Membership ? Standardized solution for storing forms authentication data ? Membership.Validate User method? Login controls wrap up membership service? Provider-based.

Download ASP.NET 2.0 Login Controls and Security.