aspdotnet-suresh offers C#articles and tutorials,csharp dot net,articles and tutorials, VB.This tutorial starts with a look at how the Roles framework associates a user's roles with his security context.Anyone could visit this page, but only authenticated users could view the files' contents and only Tito could delete the files.
A more maintainable approach is to use role-based authorization.The good news is that the tools at our disposal for applying authorization rules work equally well with roles as they do for user accounts.Following that, we will explore programmatic techniques.Before we can look at applying fine grain authorization rules, however, we first need to create a page whose functionality depends on the role of the user visiting it.However, in certain cases we may want to allow all users to visit a page, but limit the page's functionality based on the visiting user's roles.
This may entail showing or hiding data based on the user's role, or offering additional functionality to users that belong to a particular role.
It then examines how to apply role-based URL authorization rules. NET to allow only authenticated users to visit a page.
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.
If you want the cookie to be passed to all subdomains you need to customize the exists is because many user agents do not permit cookies larger than 4,096 bytes.
So this cap is meant to reduce the likelihood of exceeding this size limitation.
Figure 4: Only Users in the Administrators Role Can View the Protected Pages (Click to view full-size image) Log off and then log in as a user that is in the Administrators role.