This is a novice question but I'm having a hard time finding my specific answer so any help is appreciated...
I have a web.sitemap file that I rely on for the hierarchical definition of my site because I have all of my site's pages in the root directory (flat structure). Reason being is that I don't want to commit to a specific hierarchy because that could change radically during prototyping and maybe even in production. Since I'd like to have roles that lock down access to portions of my "virtual site hierarchy" based on roles, I'd thought I'd be in great shape when I saw the roles attribute . I could, say, define a node as having Admin role permissions so that everything below it would inherit appropriately. But, this seems to only govern the behavior of the sitemap control(s) using securityTrimming, it doesn't seem to effect the asp.net authorization mechanism. Since authorization is run from the web.config's definitions, it seems li ...
Go to the complete details ...