I would like to be able to protect individual pages with individual passwords (no username) or allow access through our custom security module.
I'm thinking of writing a module to 'override' the native Public Access dialog and write my own interface to allow user to define these settings. The only thing I'm struggling with is where/how to store the password/user access list data. Forum posts suggest storing custom data in tables within the umbraco database, or in another database. My problem with this is that it doesn't benefit from the in-built Umbraco caching.
For every page access page I would need to check against the database; firstly, whether the page has protection defined and secondly, who has access. Should I be implementing my own cache for this data or is there a data structure provided by the Umbraco API that I can take advantage of?
Hmmm, I'm not sure there's something built in that you can get to for the caching, but it should be pretty easy to write your own caching stuff to cache your data to check against. We've done that previously with custom database table data to minimise database use on the front end.
Protecting public access using custom node properties
Hi,
I would like to be able to protect individual pages with individual passwords (no username) or allow access through our custom security module.
I'm thinking of writing a module to 'override' the native Public Access dialog and write my own interface to allow user to define these settings. The only thing I'm struggling with is where/how to store the password/user access list data. Forum posts suggest storing custom data in tables within the umbraco database, or in another database. My problem with this is that it doesn't benefit from the in-built Umbraco caching.
For every page access page I would need to check against the database; firstly, whether the page has protection defined and secondly, who has access. Should I be implementing my own cache for this data or is there a data structure provided by the Umbraco API that I can take advantage of?
Thanks
Hmmm, I'm not sure there's something built in that you can get to for the caching, but it should be pretty easy to write your own caching stuff to cache your data to check against. We've done that previously with custom database table data to minimise database use on the front end.
is working on a reply...