The server supports authentication and authorization through the use of locally stored access control lists (ACLs), which describe what access rights a user has for a resource. For example, an entry in an ACL can grant a user named John read permission to a particular folder, misc.
This section describes the process of restricting access to the files or directories on your web site. You can set global access control rules for all servers, and also individually for specific servers. For instance, a human resources department might create ACLs allowing all authenticated users to view their own payroll data, but restrict access to updating data to only human resource personnel responsible for payroll.
The core ACLs supported by the server are three types of authentication: basic, SSL, and digest.
For editing access control settings, perform the following tasks:
Click Configurations tab and select the configuration.
Click Security sub tab > Access Control sub tab.
Click Add ACL button to add a new ACL or click existing ACL to edit the settings.
The following section describes the process of adding a new ACL to the configuration.
Click Configurations tab and select the configuration.
Click Access Control sub tab > Access Control Lists sub tab.
Click New button to add a new ACL.
Configure the following parameters:
Table 7–2 ACL Parameters
Using CLI
For adding an ACL through CLI, execute the following command.
wadm> set-acl --user=admin --password-file=admin.pwd --host=serverhost --port=8989 --vs=config1_vs_1 --config=config1 --aclfile=aclfile1 |
See CLI Reference, set-acl(1).
The section describes the process of adding a new Access Control Entry (ACE) for the selected configuration.
Click Configurations tab and select the configuration.
Click Access Control sub tab > Access Control List sub tab.
Click New button.
Click New button under Access Control Entry.
Configure the following ACE parameters:
Table 7–3 ACE parameters