Technically, I didn't need to specify values for these attributes since I just assigned them to their default values, but I put them here to make it explicitly clear that I am not using persistent cookies and that the cookie is both encrypted and validated. Henceforth, the Roles framework will cache the users' roles in cookies.
If the user's browser does not support cookies, or if their cookies are deleted or lost, somehow, it's no big deal – the Note Microsoft's Patterns & Practices group discourages using persistent role cache cookies.
In particular, we created a page that listed the contents of the current directory.
Anyone could visit this page, but only authenticated users could view the files' contents and only Tito could delete the files.
Applying authorization rules on a user-by-user basis can grow into a bookkeeping nightmare.
A more maintainable approach is to use role-based authorization.
The default value is "/", which informs the browser to send the authentication ticket cookie to any request made to the domain. The default value is an empty string, which causes the browser to use the domain from which it was issued (such as
Following that, we will look at using declarative and programmatic means for altering the data displayed and the functionality offered by an ASP. Or we could dictate that only users Tito and Bob were allowed, or indicate that all authenticated users except for Sam were permitted.
In addition to URL authorization, we also looked at declarative and programmatic techniques for controlling the data displayed and the functionality offered by a page based on the user visiting.
This tutorial starts with a look at how the Roles framework associates a user's roles with his security context.
It then examines how to apply role-based URL authorization rules. NET to allow only authenticated users to visit a page.