user=commercial long name = Commercial end user user=production long name = Production end user user=savignon long name = Joël Savignon end user
user=cal1 long name = Calendar RW end user user=cal1ro read only = true data id = cal1 long name = Calendar RO end userdata id = cal1 means that the data of cal1ro is the data of cal1. The calendar cal1ro is the same as cal1 except that you can't modify events in it. This calendar will appear with a small
The file /home/httpd/html/wcal/cal1/.htaccess can be for example:
AuthType Basic AuthUserFile /usr/local/apache/conf/htpasswd.users AuthName "Calendar RW" Require johnAnd the file /home/httpd/html/wcal/cal1ro/.htaccess can be for example:
AuthType Basic AuthUserFile /usr/local/apache/conf/htpasswd.users AuthName "Calendar RO" Require jackLogin/password will be prompt when accessing to the different calendars. For more information about Apache access restriction, see the Apache documentation on the Apache web site.
Important : don't create manually the .htaccess files in the web directories but use the access file resource in the wcal.conf file. .htaccess files will be generated from the value of this resource.
Groups can contain users but also other groups (subgroups). So you can have a complete users tree and you can use the data id resource to create links between them.
Groups are defined with the group resource. This is an example of a users tree definition.
group=group1 long name = Group 1 group=group11 long name = Group 1.1 user=us111 long name = User 1.1.1 end user user=us112 long name = User 1.1.1 data id = us22 end user end group user=us11 long name = User 1.1 end user user=us12 long name = User 1.2 end user end group group=group2 long name = Group 2 user=us21 long name = User 2.1 end user user=us22 long name = User 2.2 end user end groupYou can restrict access to some groups by adding a access file resource in the group section.