Security Triming is achieved by putting a web.config in each folder... each aspx file has its own folder denies * all users, and db tables in the app_data folder can be maintained with the website administration tool
wwebadmin tool can be started from website->configuration then you click on the security link, then manage users so there's two layers of security, the ones in the app_data folder and the ones in web.config that overide
app_data.
Web adminstration tool can use both both form and windows authentication, windows is handled by iis there is a control for the login button, and one to display the login user user in the sitemap section of the web.config needs to say securityTrimming enabled if a node doesnt have a page associated with it, the node needs to have roles attribute to allow to access to any pages in it's subfolder, or is this just to show the menu item in the sitepath control?
Giving roles to a sitemap node just show the node doesnt give access to the page, this is done in the child web.config files
wwebadmin tool can be started from website->configuration then you click on the security link, then manage users so there's two layers of security, the ones in the app_data folder and the ones in web.config that overide
app_data.
Web adminstration tool can use both both form and windows authentication, windows is handled by iis there is a control for the login button, and one to display the login user user in the sitemap section of the web.config needs to say securityTrimming enabled if a node doesnt have a page associated with it, the node needs to have roles attribute to allow to access to any pages in it's subfolder, or is this just to show the menu item in the sitepath control?
Giving roles to a sitemap node just show the node doesnt give access to the page, this is done in the child web.config files
Comments
Post a Comment