Upgrade your Internet Experience
Microsoft.com
Welcome Sign in
ASP.NET Developer Center
Click to Rate and Give Feedback
MSDN
MSDN Library
Visual Studio 2005
Visual Studio
Learning More
 Walkthrough: Filtering Site-Map Nod...

  Switch on low bandwidth view
This page is specific to
Microsoft Visual Studio 2005/.NET Framework 2.0

Other versions are also available for the following:
Visual Web Developer 
Walkthrough: Filtering Site-Map Nodes Based on Security Roles 

A common requirement for Web sites is to restrict access to certain pages. The combination of ASP.NET role management and ASP.NET URL authorization provide a way to restrict access to Web files based on security roles. Site maps complete the story by using a feature called security trimming to hide the navigational links to those restricted files, also based on roles.

A role is the name of a group of users. After establishing roles, you can assign individual user accounts to a role. You can restrict access to Web files and nodes in site maps based on roles.

During this walkthrough, you will learn how to do the following:

  • Create a Web site with membership and user login.

  • Establish roles for the Web site and assign user accounts to those roles.

  • Create URL authorization rules that selectively grant or deny access to pages.

  • Create a site map and enable security trimming.

  • Create a navigation menu on a Web page.

In order to complete this walkthrough, you will need the following:

  • Microsoft Visual Web Developer.

  • The .NET Framework.

  • Internet Information Services (IIS) installed locally on your computer.

  • This walkthrough also requires a way to identify individual user accounts. In working applications, you can identify users in various ways, including by their Windows user account. However, in this walkthrough, users will identify themselves by logging in to your site. Therefore, this walkthrough requires that you have a site that is configured to use ASP.NET membership and forms authentication. If you have a site that is already configured with membership, you can use that site as a starting point for this walkthrough.

Before you work with ASP.NET membership and roles, you must have an available Web site, and then you need to configure that Web site to enable membership and set up roles. If you have already completed Walkthrough: Creating a Web Site with Membership and User Login (Visual Studio), you can use the Web site that you configured in that walkthrough.

Creating a Web Site

If you already have created a Web site in Visual Web Developer, (for example, Walkthrough: Creating a Basic Web Page in Visual Web Developer), you can use that Web site and skip to the next section. Otherwise, create a new Web site and page by following these steps.

To create a local IIS Web site

  1. Open Visual Web Developer.

  2. On the File menu, click New Web Site.

    The New Web Site dialog box appears.

  3. Under Visual Studio installed templates, click ASP.NET Web Site.

  4. In the Language drop-down list, click the programming language in which you prefer to work.

  5. In the Location drop-down list, select HTTP.

    Alternatively, you can select File System if you do not have an IIS server available. However, using HTTP mimics a real-world deployment scenario, and allows you to test your pages by viewing them in a browser.

  6. Click Browse.

    The Choose Location dialog box appears. If you selected HTTP in the previous step, the Local IIS button should be selected. If not, click Local IIS.

  7. Select the Default Web Site node.

  8. Click the Create New Web Application icon (in the top right corner), and then name the new Web site SiteNavigation.

  9. Click Open, and then Click OK.

    Visual Web Developer creates the Web site and opens a new page named Default.aspx. By default, Visual Web Developer creates new pages with a matching code-behind file — Default.aspx.cs, in this case. You can change this when you create subsequent new pages using the Add New Item wizard.

    NoteNote

    Sometimes, if a previous version of the .NET Framework was installed before Visual Web Developer, you might get an error about configuring the Web site to use the latest version of the .NET Framework. You can correct this by clicking Yes on the dialog box that appears, to enable ASP.NET version 2.0 on your server, or by using IIS Manager. In IIS Manager, right-click your application, click Properties, and then click the ASP.NET tab. Beside ASP.NET Version, select the version of the .NET Framework that was installed with Visual Web Developer.

Enabling Membership and Creating a User

If you do not already have membership enabled, use the following procedure to enable it. Otherwise, go to the next section.

To enable membership

  1. In Visual Web Developer, on the Web site menu, click ASP.NET Configuration.

    The Web Site Administration Tool appears.

  2. Click the Security tab, under Users, click Select authentication type, click From the Internet, and then click Done.

    This option specifies that your application will use Forms authentication, where users will log in to the application by using a login page that you will create later in this walkthrough.

  3. On the Security tab, click Create User.

    You are going to create two user accounts for your application.

  4. In the Create User box, type information that defines a user of your application. Use the following values as guidelines. You can use any values that you like, but be sure to note your entries for use later in this walkthrough.

    • User Name   Use the name, Customer01, which is the name of our first user account.

    • Password   Use a password of your choice, preferably a strong password, which is a password that contains a minimum of eight characters, and includes uppercase and lowercase letters as well as punctuation.

    • E-mail   Use a properly formatted e-mail address. Alternatively, you can use a non-existent e-mail address because this walkthrough does not include sending e-mail.

    • Security Question and Security Answer   Type a question and answer that can be used later, if you need to recover your password.

  5. Select the Active User check box, and then click Create User.

  6. On the confirmation page, click Continue.

  7. Repeat the preceding three steps to create one more user account named Employee01. (When you create roles for these user accounts, you will use names with all lowercase letters.)

  8. Click the Back button at the bottom right corner of the page to return to the Security start page.

Creating a User Login Page

To test the membership and role settings that you will configure later in this walkthrough, you need to create a way for users to log in so that you can identify them.

To create a default page for all users that displays login status

  1. Open the Default.aspx page, and then switch to Design view.

    If you do not have a Default.aspx page, add one to the root of your Web site.

    NoteNote

    Be sure to name the page Default.aspx; this name is used later in this walkthrough.

  2. In the Toolbox, from the Login group, drag a LoginStatus control onto the page.

    The LoginStatus control automatically takes users to the Login.aspx page, if they have not already logged in.

  3. Place the cursor to the right of the LoginStatus control, press ENTER, and then type the following, including the extra space: Hello .

  4. In the Toolbox, from the Login group, drag a LoginName control onto the page.

    The LoginName control will display the user's name, if the user is logged in.

  5. Save the page, and then close it.

You now have a home page that is available to all users. The next step is to create a simple login page.

To create a login page

  1. Add a page named Login.aspx to the root of your Web site.

  2. Open the Login.aspx page, and then switch to Design view.

  3. In the Toolbox, from the Login group, drag a Login control onto the page.

  4. Right-click the Login control, click Properties, and then set DestinationPageUrl to Default.aspx.

  5. Save the page, and then close it.

Before you work with security trimming, you must set up user roles.

Enabling Roles

In order to make security trimming work, roles must be enabled.

To enable roles

  1. In Visual Web Developer, on the Website menu, click ASP.NET Configuration.

    The Web Site Administration Tool appears.

  2. Click the Security tab, and then click Enable roles.

Creating Roles and Assigning User Accounts to Those Roles

Roles are now enabled, but until you create a role and assign user accounts to those roles, you cannot create access rules.

To create roles and assign user accounts

  1. If the Web Site Administration Tool is not open, follow these steps to open it: In Visual Web Developer, on the Web site menu, click ASP.NET Configuration.

    The Web Site Administration Tool appears.

  2. Click the Security tab, and then click Create or Manage roles.

    You are going to create two roles.

  3. In the Create New Role box, type customers, and then click Add Role.

  4. Repeat the preceding step to create a role named employees.

  5. In the Role Name box, next to customers, click Manage.

    This takes you to a page where you can select user accounts from a list to add to the customers role.

  6. In the Search for Users box, click All.

    This displays all of the user accounts for your Web site. You can also search by the first letter of the user's name if your list is too long.

  7. Next to the user name Customer01, select the box in the User Is In Role column.

    The user Customer01 is now a member of the customers role.

  8. Click Back to return to the Create New Role page.

  9. Repeat the preceding two steps to add the user Employee01 to the employees role.

  10. Close the ASP.NET application administration page.

In order to test security trimming, you need to create some folders and pages for your Web site, and then set security permissions on those folders and pages.

Creating Necessary Folders and Pages for this Walkthrough

Your Web site will contain a site map structure that links to a few pages, which you can create now.

To create the necessary folders and pages

  1. In Solution Explorer, right-click the root of your Web site, click New Folder, and then name the folder EmployeesOnly.

    The EmployeesOnly folder will contain a page that is accessible to only some of your users.

  2. Right-click the root of your Web site, click New Folder, and then name the folder Customers.

    The Customers folder will also contain a page that is accessible to only some of your users.

  3. In the EmployeesOnly folder, create a new page named Discounts.aspx.

  4. In the Customers folder, create a new page named Support.aspx.

  5. In the root of your Web site, create four new pages named Hardware.aspx, Software.aspx, Training.aspx, and Consulting.aspx.

  6. In each of the new pages you have created, switch to Design view, type the page title of the top of the page, and then format the title as <H1> so that you can identify the page when you browse to it.

  7. Save the new pages and then close them.

Creating Access Rules

The Web site that you are creating will allow users to gain access to different pages according to their roles. Therefore, you need to create some access rules that determine which roles have access to which folders.

To set up access rules for the EmployeesOnly folder

  1. In Visual Web Developer, on the Web site menu, click ASP.NET Configuration.

    The Web Site Administration Tool appears.

  2. On the Security tab, click Manage access rules, and then click Add new access rules. This takes you to the Add New Access Rule page.

  3. Under Select a directory for this rule, expand the root node, and then click EmployeesOnly.

  4. Under Rule applies to, click Role, and then in the box, click employees.

  5. Under Permission, select Allow.

    The rule that you have created grants access permissions for the EmployeesOnly folder to anyone in the employees role.

  6. Click OK.

    The new rule is displayed in a grid in the Manage Access Rules table. When users request a page from the EmployeesOnly folder, the rules are checked in order, from top to bottom, to determine whether the user is allowed access to the page. If the user is not part of the employees role, the pages in this folder will not be displayed.

  7. Click the Add new access rule link.

  8. Under Rule applies to, select All Users.

  9. Under Permission, select Deny, and then click OK.

    The second rule for the EmployeesOnly folder makes sure that no one except users in the employees role can gain access to the folder. The rules are processed in order, from top to bottom, as you see them in the grid.

    The first rule (Allow) grants access to users in the role of employees. The second rule (Deny) denies access to all other users. You can create as many Allow or Deny rules as you need for your application. When users request a page from the EmployeesOnly folder, the rules are checked in order, from top to bottom, to determine whether the user is allowed access to the page.

The next step repeats the preceding procedure for the Customers folder. However, both the customers and employees roles can be used to gain access to the Customers folder. As an example of a real-world scenario, consider a company that wants their phone support employees to have access to the same pages that customers can see.

To set up access rules for the Customers folder

  1. Click the Add new access rule link.

  2. Under Rule applies to, select the Role box, and then in the box, click customers.

  3. Under Permission, select Allow, and then click OK.

    The rule you have created grants access permissions for the Customers folder to anyone in the customers role.

  4. Under Manage access rule, click Customers.

  5. Click the Add new access rule link.

  6. Under Rule applies to, select the Role box, and then in the box, click employees.

  7. Under Permission, select Allow, and then click OK.

    The rule that you have created grants access permissions for the Customers folder to anyone in the employees role, as well.

  8. Under Manage access rule, click Customers.

  9. Click the Add new access rule link.

  10. Under Rule applies to, select the All Users box.

  11. Under Permission, select the Deny box, and then click OK.

    The first and second rules for the Customers folder makes sure that no one except users with an account in the customers role or the employees role can gain access to the Customers folder. The rules are processed in order, from top to bottom, as you see them in the grid.

    The first rule (Allow) grants access to users with an account in the role of members. The second rule (Deny) denies access to all other users. You can create as many Allow or Deny rules as you need for your application. When users request a page from the Customers folder, the rules are checked in order, from top to bottom, to determine whether the user is allowed access to the page.

  12. Click Done to return to the Security tab.

In this part of the walkthrough, you will create a site map to describe the navigation structure of your Web site, and then enable security trimming of site-map nodes by editing the Web.config file.

Creating a Site Map

To use site navigation, you need a way to describe how the pages in your site are laid out. The default method is to create an XML file that contains the site hierarchy, including the page titles and URLs.

Each page is represented as a siteMapNode element in the site map. The top-most node represents the home page, and child nodes represent pages that are deeper in the site.

To create a site map

  1. In Solution Explorer, right-click the name of your Web site, and then click Add New Item.

  2. In the Add New Item dialog box:

    1. Under Visual Studio installed templates, click Site Map.

    2. Make sure that the name in the Name box is Web.sitemap.

      NoteNote

      The file must be named Web.sitemap and must appear in the root of your Web site.

    3. Click Add.

  3. Copy the following XML content into the Web.sitemap file, overwriting the default contents of the XML file.

    <?xml version="1.0" encoding="utf-8" ?>
<siteMap>
  <siteMapNode title="Home" description="Home" 
       url="~/default.aspx" >
    <siteMapNode title="Products" 
         description="Our products" 
         roles="*">
      <siteMapNode title="Hardware" 
           description="Hardware we offer" 
           url="~/Hardware.aspx" />
      <siteMapNode title="Software" 
           description="Software for sale" 
           url="~/Software.aspx" />
      <siteMapNode title="Discounts" 
           description="Employee Discounts" 
           url="~/EmployeesOnly/Discounts.aspx" />
    </siteMapNode>
    <siteMapNode title="Services" 
         description="Services we offer" 
         roles="*">
      <siteMapNode title="Training" 
           description="Training" 
           url="~/Training.aspx" />
      <siteMapNode title="Consulting" 
           description="Consulting" 
           url="~/Consulting.aspx" />
      <siteMapNode title="Support" 
           description="Support" 
           url="~/Customers/Support.aspx" />
    </siteMapNode>
  </siteMapNode>
</siteMap>

    The Web.sitemap file contains a set of siteMapNode elements that are nested to three levels. The structure of each element is the same; the only difference among them is their location within the XML hierarchy.

    The URL of the pages that are defined in the sample XML file are unqualified, meaning that all of the pages will be treated as having URLs relative to the application root. However, you can specify any URL for a given page — the logical structure that you define in the site map does not have to correspond to the physical layout of the pages in folders.

    The roles attribute is only set on two nodes in the site map: Products and Services. These two nodes do not have a url attribute. ASP.NET uses the access rules of an .aspx page to verify whether the site-map node should be visible to a user. Without a url attribute, no user can view the page if security trimming is enabled. Setting the roles attribute to an asterisk (*), or a wildcard character, expands access to everyone.

  4. Save the file, and then close it.

Enabling Security Trimming

The site map that you created uses the default site-map provider, XmlSiteMapProvider. For this reason, the Web.config file does not need to contain a siteMap Element (ASP.NET Settings Schema) element because ASP.NET has an intrinsic configuration for default site maps. However, security trimming is not enabled by default, so the siteMap Element (ASP.NET Settings Schema) element must be set.

To enable security trimming

  1. In Visual Web Developer, right-click the root of your Web site, and then click Refresh Folder.

    This makes the Web.config file appear in Solution Explorer. The Web.config file can be created by selecting Add New Item or by using the ASP.NET Configuration tool as we did earlier in this walkthrough.

  2. Open the Web.config file.

  3. Look for a siteMap Element (ASP.NET Settings Schema) element in case it already exists.

    If the siteMap Element (ASP.NET Settings Schema) element does not exist, paste the following code inside the system.web Element (ASP.NET Settings Schema) element, being careful not to paste it inside any other element.

    <siteMap defaultProvider="XmlSiteMapProvider" enabled="true">
  <providers>
    <add name="XmlSiteMapProvider"
      description="Default SiteMap provider."
      type="System.Web.XmlSiteMapProvider"
      siteMapFile="Web.sitemap"
      securityTrimmingEnabled="true" />
  </providers>
</siteMap>

  4. Save the Web.config file, and then close it.

The security-trimming feature uses URL authorization on each request to determine whether a user has access to a URL that is associated with a siteMapNode element. This extra work reduces performance depending on the number of nodes being authorized. When security trimming is enabled, you can use the following methods to improve performance:

  • Limit the number of nodes in the site-map file   Site-map files with more than 150 nodes can take substantially longer to perform security-trimming operations.

  • Set the roles attribute explicitly on siteMapNode elements   Note that setting the roles attribute to an asterisk (*) should be used for nodes that can safely be displayed to any client. The presence of a roles attribute allows ASP.NET to bypass URL authorization for the URL that is associated with the siteMapNode when a user belongs to one of the roles listed in the attribute.

Now that you have a site map and some pages, you can add navigation to your site.

Alternatively, you can use a SiteMapPath or Menu control to display site navigation. For more information, see Navigation ASP.NET Controls or Walkthrough: Adding Site Navigation to a Web Site.

Creating a Navigation Menu with the TreeView Control

You will use the TreeView control to act as a collapsible navigation menu.

To add a navigation menu

  1. Open the Default.aspx page, and then switch to Design view.

  2. In the Toolbox, from the Data group, drag a SiteMapDataSource control onto the page.

    In its default configuration, the SiteMapDataSource control gets its information from the Web.sitemap file that you created previously, so you do not need to specify any additional information for the control.

  3. In the Toolbox, from the Navigation group, drag a TreeView control onto the page.

    The TreeView Tasks menu appears.

  4. On the TreeView Tasks menu, in the Choose Data Source box, click SiteMapDataSource1.

  5. Save the page.

Creating a Navigation Menu with the SiteMapPath Control

You will use the SiteMapPath control to act as a breadcrumb-style navigation display that shows users the path back to the root page.

To add a navigation menu

  1. Open the Hardware.aspx page, and then switch to Design view.

    To illustrate how the SiteMapPath control works, place the control on a deeply nested page.

  2. If you added a title inside <H1> tags on this page, place your cursor at the right side and press ENTER.

  3. In the Toolbox, from the Navigation group, drag a SiteMapPath control onto the page.

    The SiteMapPath Tasks menu appears, but there is no need to configure a data source.

  4. Save the page.

Your site is now ready for testing.

To test security trimming

  1. Switch to the Default.aspx page, and then press CTRL+F5 to run the page.

    In the TreeView control, you should not see the Discounts or Support links.

  2. Click Login.

  3. Log in as Customer01, which is a user account that is in the customers role.

    In the TreeView control, you should now see the Support link.

  4. Click Logout, and then click Login.

  5. Log in as Employee01, which is a user account that is in the employees role.

    In the TreeView control, you should now see both the Discounts link and the Support link. As an employee, you should see all of the available links because none of the links are restricted for employees.

  6. On the Default.aspx page, click Hardware so that you can see the SiteMapPath control.

    The SiteMapPath control should display the path from the home page to the Hardware page.

In the current state of the Web site, the navigation tree appears only on the home page. You could add the same SiteMapDataSource and TreeView controls to each page in the application to display a navigation menu on each page. Alternatively, you could put the navigation tree on a master page so that it automatically appears with every page that is referenced by the master page file.

This walkthrough illustrates the basic functionality of ASP.NET site navigation: navigation controls, roles management, and security trimming. You might want to experiment with additional features of navigation. For example, you might want to put your navigation controls in a master page in order to have them show up on all pages that reference the master page. For details, see Walkthrough: Creating and Using ASP.NET Master Pages in Visual Web Developer

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker