FW: [opencms-dev] Access groups for OpenCms sub sites.

[Sebastian Himberger]

Hi Olli,

we have a setup for multisite hosting although it does not scale without
automating some tasks.

We have set the permissions for the Users group on the sites/ folder to:
+ override inherited
+ inherit on subfolder
(nothing more is checked)

Then we added two groups for each customer: customer - user, customer -
manager and applied the permissions on the corresponding sites subfolder
(e.g. /sites/customerA). This setup works quite well but we ran into
another problem: The template selectbox needs access to the templates
subfolder so we could not use a similar setting here. In order to
cleanly seperate templates from customers we had to explicitly deny the
templates of customerA to all other customers. As we reached this point
we decided to write a small workplace utility which manages hosted
sites. It keeps track of the permissions and even modifies the OpenCms
config files and creates the virtual hosts for apache based on a
velocity template. I don't think we can give it away at this point
(because it's "a grown system",only developed for internal use and we
currently don't have the resources to support it properly) but if you
have further questions or thoughts you can of course send me an e-mail.

best regards
Sebastian




Olli Aro schrieb:
>
> Anyone have any views on this?
>
>  
>
> Olli
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* opencms-dev-bounces at opencms.org
> [mailto:opencms-dev-bounces at opencms.org] *On Behalf Of *Olli Aro
> *Sent:* 17 January 2007 15:43
> *To:* 'The OpenCms mailing list'
> *Subject:* [opencms-dev] Access groups for OpenCms sub sites.
>
>  
>
> Hi all,
>
>  
>
> I am currently setting up an ASP service based on OpenCms, which gives
> each client completely independent sub site in OpenCms. As part of
> this it is important that editors for each site can only access their
> own content.
>
>  
>
> I would be interested to know, if people have any best practices for
> this kind of groups set up? The way I have currently achieved this is
> to create each sub site an “access denied” group and then place the
> editors for all other sites to that group. However, this is not very
> scalable, since if I introduce a new sub site, I always must ensure
> that the existing editors are added to “access denied” group for that
> sub site. Initially I did try to restrict permissions for default
> “Users” group and then make the editors part of “access allowed”
> group, but it seems that if the “Users” group does not have certain
> permissions the sub site will not appear in the “sub sites” drop down.
>
>  
>
> Any alternatively approaches greatly appreciated J
>
>  
>
> Regards,
>
>  
>
> Olli
>
>  
>
>  
>
>  
>
> ------------------------------------------------------------------------
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
> ------------------------------------------------------------------------
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev