Moe Tarhini
Member
- Joined
- Jul 9, 2003
- Messages
- 15
The solution is to implement your own HTTP Module and determine the allow / deny security based upon the roles attribute in the Web.sitemap file. This works in conjunction with ASP.NET 2.0s built-in security.
Add the following code to your web.config file inside the <system.web> node. This will allow you to intercept requests to all pages before processing, allowing you to force the Web.sitemap security.
<httpModules> <add name="SecurityHttpModule" type="Joel.Net.SecurityHttpModule" /></httpModules>
Heres the code that performs all the magic... View Source Code
Moe Tarhini
Senior Software Engineer
http://profoundway.blogspot.com
Add the following code to your web.config file inside the <system.web> node. This will allow you to intercept requests to all pages before processing, allowing you to force the Web.sitemap security.
<httpModules> <add name="SecurityHttpModule" type="Joel.Net.SecurityHttpModule" /></httpModules>
Heres the code that performs all the magic... View Source Code
Moe Tarhini
Senior Software Engineer
http://profoundway.blogspot.com