Hi Will, Yes, I agree - keeping the public users in a clustered repo is the way to go. Just not in the main users repo, in my opinion!
My mail suggested storing the public users (and only the public users, not the other ones) in their own workspace, separate from the system and admin users. In this way you can keep the public users clustered, and the system and admin users unclustered. It was my impression that there are differences between the public user databases and the author user databases even in the default state, but maybe I am wrong on that. For us there certainly are differences now that we are using the system: we don't publish all our users, only the ones that are supposed to activate content. If you create a cluster over the users workspace, it will also mean all users are "instantly" published, so all users will have the same privileges on public and author systems (unless you define the roles differently, but that would be confusing!). But maybe one doesn't want one's editors to be able to log into the public system... Also, as a general principle, I don't like the "smell" of the public user registration writing into the same workspace as the privileged users are stored in. It seems to me that security is better if these are separated, and the PUR never writes into the workspace that the author system is using to store its user infos... Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Will Scheidegger Gesendet: Mittwoch, 16. Jänner 2013 15:17 An: Magnolia User-List Betreff: Re: [magnolia-user] JCR Cluster Config ? Hi Richard Can you elaborate a bit on why not storing users in a clustered repo? I get the argument about roles, but what can be different in the user node between author and public. When you allow public users to update something in their profile, then have the need to reset their password (or anything alike it) you would overwrite their changes when you hold the user data in two separate repos and activate the users from author to public. In these cases I would say it makes a lot of sense to keep the public users in a clustered repo. -will ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
