9: Security and Personalization | in VS .NET

Generation QR Code JIS X 0510 in VS .NET 9: Security and Personalization |

7. You need to add a line to web.config, setting profile enabled to true. You also need to add a <properties> section within the profile section, and use the <add> property to specify the names of the properties you want to retain. 8. Use an anonymous profile by setting <anonymousIdentification enabled="true"> in the web.config file. 9. Style sheet themes are functionally equivalent to CSS style sheets, and can be overridden by the page or by the control. Customization themes are applied last, and therefore cannot be overridden. 10. You define the settings for a skin in a .skin file, which resides inside a folder named after the theme, which in turn is located with the App_Themes folder of your site.

Exercise 9-1. Create your new web site. Start off by deleting Default.aspx. Add a new page Home.aspx, set it as the start page, give it a title and an <h1>, and then add a LoginStatus control. Add a LoginView control, and set the Logged In and Logged Out templates to the appropriate messages. Add a LoginName control to the Logged In template to greet the user by name. If you re not going to use the WAT to create any users, you need to add the following line to your web.config file, in the <system.web> section:

Add a new page to your site, login.aspx. Give it a title and an <h1>, and then drag a Login control onto the page. Give it whatever formatting you like. At the moment, though, the only way to create a new user is with the WAT. Add a page where users can create their own user accounts. Create a new page, CreateAccount.aspx. Give it a title and an <h1>, and then add a CreateUserWizard control to the page. Set the ContinueDestination property to Home.aspx to take users back to the front of the site when they ve created their accounts. Go back to the Login. aspx page, and add a Hyperlink control with a NavigateUrl property of CreateAccount. aspx, so that users can create an account if they don t already have one. Run your site and create a handful of users to populate your database. Be sure to write down the passwords because you ll need them later. Exercise 9-2. Create the content pages first, fishforum.aspx and siteadmin.aspx. The next thing you ll need to do is define roles for your existing users. You can only do that from the WAT, so start up the WAT (Website ASP.NET Configuration), select Security, click Enable Roles, click Create or Manage Roles, and add two roles for Moderator and User. Then go back, click Manage Users, and add some of your users to the Moderator group, and all of them to the User group. Close the WAT.

|

Open siteadmin.aspx.vb. You want to restrict access to this page to just users who have the Moderator role. Create an event handler for the Page Load event as usual, and add this code:

This allows Moderators to view the page, but plain users will be sent back to the home page. Open siteadmin.aspx and add some text indicating that this is a placeholder page for content to come. Add a hyperlink and set the NavigateUrl property to Home.aspx. Now open fishforum.aspx.vb. You want only people in the User role to be able to access this page, so create a Page Load event for this page and add the following code:

Users who are in the User role will be able to view this page, but anyone else will be sent back to the home page. Open fishforum.aspx and also add some text indicating that this is a placeholder page for content to come. Add a hyperlink and set the NavigateUrl property to Home.aspx. Open up Home.aspx and add two hyperlinks one that points to fishforum.aspx, and one that points to siteadmin.aspx. Test out your site. You ll find that your users in the Moderator role can visit both content pages, but users in the User role can only visit the Fish Forum. Users who aren t logged in, or don t have a role, are returned to the home page. Of course, in practice, you d redirect users to a No permissions page, but returning them to the home page is fine for now. Exercise 9-3. If you re going to use profiles, the first thing you need to do is make a modification to the web.config file. Open web.config and add the following code to enable profiles and store the four data elements you want to save:

<profile enabled="true" defaultProvider="AspNetSqlProfileProvider"> <properties> <add name="userName" /> <add name="numFish" /> <add name="fishType" /> <add name="favFish" /> </properties> </profile>