Predefined ACLs

Abstract

This document describes a feature allowing to set a predefined ACL on a given space (assuming this space is in ACL space).

Such a feature is especially useful for activities and working groups who have their home page in datespace (as the semantic web activity, the XKMS Activity) and can easily define which parts of this space is public or member only.

Features and constrains

You can define a default ACL for any new resource on a given space, defined by a directory on our web space.

What this feature provides:

• any resource created in the given space will have its ACL set to the given ACL as soon as it's created
• it works recursively on any subdirectory

What it doesn't do:

• it doesn't change ACLs on resources created before the feature has been set up
• it doesn't stop on any directory, so you need to specify if a subdirectory has a different default ACL

How to have this set up?

The simplest way is to create a .default-acl file in the given directory, containing one of "Public", "Member" or "Team", depending on the ACL you want.

For more complex ACLs or to change an existing default ACL, send your request to [email protected] with the following informations:

• the directory on which will be applied the default ACLing
• the default ACL you want on this space. If this ACL is different from "public", "member", or "team", please provide an URI to a resource which already has such an ACL.

References

• W3C ACL System
• How to set it up? (for the webteam)
• announce of .default-acl to the Team (Jun 2004)