ACL File Syntax
ACL File Syntax
All ACL files must follow a specific format and syntax. An ACL file is a text file
containing one or more ACLs. All ACL files must begin with the version number
they use. There can be only one version line and it can appear after any
comment lines. For example:
You can include comments in the file by beginning the comment line with the
# sign.
Each ACL in the file begins with a statement that defines its type. ACLs can
follow one of three types:
• Path ACLs specify an absolute path to the resource they affect
• URI (Uniform Resource Indicator) ACLs specify a directory or file relative to
• Named ACLs specify a name that is referenced in resources in the
The type line begins with the letters acl and then includes the type
information in double-quotation marks followed by a semicolon. Each type
information for all ACLs must be a unique name--even among different ACL
files. The following lines are examples of several different types of ACLs:
After you define the type of ACL, you can have one or more statements that
define the method used with the ACL (authentication statements) and the
people and computers who are allowed or denied access (authorization
statements). The following sections describe the syntax for these statements.
456 Netscape Enterprise Server Administrator's Guide
version 3.0;
the server's document root.
obj.conf file. The server comes with a "default" named resource that
allows read access to anyone and write access to users in the local database
or LDAP directory. Even though you can create a named ACL from the
Enterprise Server windows, you must manually reference the named ACLs
with resources in the obj.conf file.
acl "path=C:/Netscape/SuiteSpot/docs/mydocs/";
acl "*.html";
acl "default";
acl "uri=/mydocs/";
Need help?
Do you have a question about the Netscape Enterprise Server and is the answer not in the manual?
Questions and answers