Securing different sections of Umbraco front end - best practise
Hi There, I was hoping to get some advice on how to secure certain pages in Umbraco with making it a maintenance nightmare? My first thought is the membership provider for .net and create the users throuugh the backend etc.
Do you mean securing what site visitors (members) can see, or what site editors (users) can update?
I'm quite new to Umbraco but looks to me like either of these scenarios is handled pretty well by using roles.
For members you right click the page, choose "Public Access" and select which roles to grant access to.
For users you set what point in the content tree they can get access to.
We've got the Umbraco site hooked up to the membership database of another asp.net application although we have created specific roles in it for the web content.
Securing different sections of Umbraco front end - best practise
Hi There, I was hoping to get some advice on how to secure certain pages in Umbraco with making it a maintenance nightmare? My first thought is the membership provider for .net and create the users throuugh the backend etc.
Any other approaches that people can recommend?
Sean
Hi Sean
Do you mean securing what site visitors (members) can see, or what site editors (users) can update?
I'm quite new to Umbraco but looks to me like either of these scenarios is handled pretty well by using roles.
For members you right click the page, choose "Public Access" and select which roles to grant access to.
For users you set what point in the content tree they can get access to.
We've got the Umbraco site hooked up to the membership database of another asp.net application although we have created specific roles in it for the web content.
Hasn't gone live yet but looking good so far
is working on a reply...