You can create, edit, or delete access control for a specific server instance using the Server Manager.
While deleting you should not delete all the ACL rules from the ACL files. At least one ACL file containing a minimum of one ACL rule is required to start the server. Deleting all ACL rules and restarting the server will result in a syntax error.
To create access control for a server instance, perform the following steps:
Access the Server Manager and select the server instance you wish to create or edit ACLs for.
Choose the Preferences tab from the Server Manager.
Click the Restrict Access link.
From the Option column choose one of the following:
Add and enter the ACL file location
Edit and select the ACL file from the drop-down menu
Delete from the drop-down menu and select the ACL file
The Access Control List Management Page with three options appears:
Select one of the following:
Pick a resource to specify a wildcard pattern for files or directories (such as *.html), choose a directory or a filename to restrict, or browse for a file or directory.
Pick an existing ACL to select from a list of all the ACLs you have enabled. Existing ACLs you have not enabled will not appear in this list.
Enter the ACL name allows to create named ACLs. Use this option only if you’re familiar with ACL files. You’ll need to manually edit the obj.conf file if you want to apply named ACLs to resources.
What it means
A named ACL created during installation that restricts write access so only users in the LDAP directory can publish documents.
One set of rules determines the access to your entire web site, including any virtual servers you have running. To restrict access to a virtual server, specify the path of its document root.
Controls access to all files and directories in the cgi-bin directory. You must specify an absolute path. On Windows, the path must include the drive letter.
Controls access to the sales directory in the document root. To specify URIs, create a named ACL.
Click Edit Access Control.
The Access Control Rules for: (server instance) appears.
Select Access control is on, if it is not already selected.
To configure or edit the ACL for this server instance, click Deny in the Action column.
Select Allow, if it isn’t already selected as the default, and click Update.
Click on the Anyone field in the Users/Groups column.
The User/Group page appears in the lower frame:
Select which users and groups you will allow access to and click Update.
Clicking List for Group and User provide lists for you to choose from.
Click on anyplace in the From Host column.
Enter Host Names and IP Addresses allowed access and click Update.
Click on All field in the Rights column.
Select one of the following and then click Update:
All Access Rights
Only the following rights and check all appropriate rights for this user
(Optional) Click the x under the Extra column to add a customized ACL expression.
Put a check in the Continue column, if it isn’t already selected as the default.
The server evaluates the next line before determining if the user is allowed access. When creating multiple lines, starts with the most general restrictions to the more specific ones.
(Optional) Click Response when denied to direct the user to a different URL or URI.
Enter the path to the absolute URL or a relative URI and click update.
Click Submit to store the new access control rules in the ACL file.
Clicking Revert will remove all of the settings you’ve just created.
Repeat all steps above for each server instance you wish to establish access control for.
When finished, click Apply.
Select Hard Start/Restart or Dynamically Apply.
ACL settings can also be enabled for each virtual server. For more information, see Accessing Databases from Virtual Servers.