Previous     Contents     Index     DocHome     Next     
iPlanet Web Server, Enterprise Edition Administrator's Guide



Chapter 8   Controlling Access to Your Server


This chapter discusses the various methods you can use to control access to the Administration Server and to the files or directories on your web site. For example, for the Administration Server, you can specify who has full control of all the servers installed on a machine and who has partial control of one or more servers. Before you can use access control on the Administration Server, you must enable distributed administration from and set up an administration group in your LDAP database. This chapter assumes you have already configured distributed administration and have defined users and groups in your LDAP database.

You should also ensure the security of the web server as discussed in Securing Your Web Server

This chapter contains the following sections:



What Is Access Control?

Access control allows you to determine:

  • Who can access iPlanet Web Administration Server

  • Which programs they can access

  • Who can access the files or directories on your web site

You can control access to the entire server or to parts of the server, or the files or directories on your web site. You create a hierarchy of rules called access control entries (ACEs) to allow or deny access. Each ACE specifies whether or not the server should check the next ACE in the hierarchy. The collection of ACEs you create is called an access control list (ACL).

By default, the server has one ACL file that contains multiple ACLs. After determining the virtual server to use for an incoming request, iPlanet Web Server checks if any ACLs are configured for that virtual server. If ACLs are found that apply for the current request, iPlanet Web Server evaluates their ACEs to determine whether access should be granted or denied.

You allow or deny access based on:

  • Who is making the request (User-Group)

  • Where the request is coming from (Host-IP)

  • When the request is happening (for example, time of day)

  • What type of connection is being used (SSL)


Setting Access Control for User-Group

You can limit access to your web server to certain users or groups. User-Group access control requires users to enter a username and password before gaining access to the server. The server compares the information in a client certificate, or the client certificate itself with a directory server entry.

The Administration Server uses only the basic authenticaton. If you wish to require client authentication on your Administration Server, you must manually edit the ACL files in obj.conf changing the method to SSL.

User-Group authentication methods for server instances include:

  • Default

  • Basic

  • SSL

  • Digest

  • Other

All of these methods require a directory server.

User-Group authentication requires users to authenticate themselves before getting access to the Administration Server, or the files and directories on your web site. With authentication users verify their identity by entering a username and password, using a client certificate, or digest authentication plug-in. Using client certificates requires encryption. For information on encryption and using client certificates, see Securing Your Web Server


Default Authentication

Default authentication is the preferred method. The Default setting uses the default method you specify in the obj.conf file, or "Basic" if there is no setting in obj.conf. If you check Default, the ACL rule doesn't specify a method in the ACL file. Choosing Default allows you to easily change the methods for all ACLs by editing one line in the obj.conf file.


Basic Authentication

Basic authentication requires users to enter a username and password to access your web server or web site. It is the default setting. You must create and store a list of users and groups in an LDAP database, such as the iPlanet Directory Server. You must use a direstory server installed on a different server root than your web server, or a directory server installed on a remote machine.

When users attempt to access a resource that has User-Group authentication in the Administration Server or on your web site, the web browser displays a dialog box asking the user to enter a username and password. The server receives this information encrypted or unencrypted, depending on whether encryption is turned on for your server.

Note

Using Basic Authentication without SSL encryption, sends the username and password in unencrypted text across the network. The network packets could be intercepted, and the username and password could be pirated. Basic authentication is most effective when combined with SSL encryption, Host-IP authentication, or both. Using Digest Authentication avoids this problem.


The following dialog appears when users authenticate themselves to the server:

Figure 8-1    Example of Username and Password Prompt

After clicking OK, the user will see:

  • The Server Administration page, if authenticated to access iPlanet Web Administration Server

  • The file or directory listing requested, if logging in to a web site

  • A message denying access if the username or password was invalid

You can customize the access denied message that unauthorized users receive in the Access Denied Response page.


SSL Authentication

The server can confirm users' identities with security certificates in two ways:

  • Using the information in the client certificate as proof of identity

  • Verifying a client certificate published in an LDAP directory (additional)

When you set the server to use certificate information for authenticating the client, the server:

  • Checks first if the certificate is from a trusted CA. If not, the authentication fails and the transaction is ended. To learn how to turn on client authentication, see Requiring Client Authentication

  • Maps the certificate to a user's entry using the certmap.conf file, if the certificate is from a trusted certificate authority (CA). To learn how to set up the certificate mapping file see Using the certmap.conf File.

  • Checks the ACL rules specified for that user if the certificate maps correctly. Even if the certificate maps correctly, ACL rules can deny the user access.

Requiring client authentication for controlling access to specific resources differs from requiring client authentication for all connections to the server. If you set the server to require client authentication for all connections, the client only needs to present a valid certificate issued by a trusted CA. If you set the server's access control to use the SSL method for authentication of users and groups, the client will need to:

  • Present a valid certificate issued by a trusted CA

  • The certificate must be mapped to a valid user in LDAP

  • The access control list must evaluate properly

When you require client authentication with access control, you need to have SSL ciphers enabled for your web server. See Securing Your Web Server to learn how to enable SSL.

In order to successfully gain access to an SSL authenticated resource, the client certificate must be from a CA trusted by the web server. The client certificate needs to be published in a directory server if the web server's certmap.conf file is configured to compare the client's certificate in the browser with the client certificate in the directory server. However, the certmap.conf file can be configured to only compare selected information from the certificate to the directory server entry. For example, you could configure the certmap.conf file to only compare the user ID and email address in the browser certificate with the directory server entry. To learn more about certmap.conf and certificate mapping, see Securing Your Web Server

Note

Only the SSL authentication method requires modification to the certmap.conf file, because the certificate is checked against the LDAP directory. Requiring client authentication for all connections to the server does not. If you choose to use client certificates, you should increase the value of the AcceptTimeout directive in magnus.conf.



Digest Authentication

Digest authentication allows the user to authenticate based on username and password without sending the username and password as cleartext. The browser uses the MD5 algorithm to create a digest value using the user's password and some information provided by the Web Server. This digest value is also computed on the server side using the Digest Authentication plug-in, and compared against the digest value provided by the client. If the digest values match, the user is authenticated.

In order for this to work, your directory server needs access to the user's password in cleartext. iPlanet Directory Server 5.0 includes a reversible password plug-in using a symmetric encryption algorithm to store data in an encrypted form, that can later be decrypted to its original form. Only the Directory Server holds the key to the data.

For digest authentication, you need to enable the reversible password plug-in and the digestauth-specific plug-in included with iPlanet Web Server 6.0. To configure your web server to process digest authentication, set the digestauth property of the database definition in dbswitch.conf.

The server tries to authenticate against the LDAP database based upon the ACL method specified, as shown in Table 8-1. If you do not specify an ACL method, the server will use either digest or basic when authentication is required, or basic if authentication is not required. This is the preferred method.


Table 8-1    Digest Authentication Challenge Generation

ACL Method

Digest Authentication Supported by Authentication Database

Digest Authentication Not Supported by Authentication Database

"default"

none specified  

digest and basic  

basic  

"basic"  

basic  

basic  

"digest"  

digest  

ERROR  

When processing an ACL with method = digest, the server attempts to authenticate by:

  • Checking for Authorization request header. If not found, a 401 response is generated with a Digest challenge, and the process stops.

  • Checking for Authorization type. If Authentication type is Digest the server then:

    • Checks nonce. If not a valid, fresh nonce generated by this server, generates 401 response, and the process stops. If stale, generates 401 response with stale=true, and process stops.

    • Checks realm. If it does not match, generates 401 response, and process stops.

    • Checks existence of user in LDAP directory. If not found, generates 401 response, and process stops.

    • Gets request-digest value from directory server and checks for match to client's request-digest. If not, generates 401 response, and process stops.

    • Constructs Authorization-Info header and inserts into server headers.


Installing the Digest Authentication Plug-in on Unix
The Digest Authentication plug-in consists of a shared library found in both:

  • libdigest-plugin.lib

  • libdigest-plugin.ldif

To install the Digest Authentication plug-in on Unix, perform the following steps:

  1. Make sure this shared library resides on the same server machine that the iPlanet Directory Server is installed on.

  2. Make sure you know the Directory Manager password.

  3. Modify the libdigest-plugin.ldif file changing all references to /path/to to the location where you installed the digest plug-in shared library.

  4. To install the plug-in, enter the command:

    % ldapmodify -D "cn=Directory Manager" -w password -a < libdigest-plugin.ldif


Installing the Digest Authentication Plug-in on NT
You will need to copy several .dll files from the iPlanet Web Server installation to your iPlanet Directory Server server machine in order for iPlanet Directory Server to start properly with the Digest plug-in.

To install the Digest Authentication plug-in on NT, perform the following steps:

  1. Access the shared libraries in the iPlanet Web Server installation in:

    [server_root]\bin\https\bin

  2. Copy the files:

    • nsldap32v50.dll

    • libspnr4.dll

    • libplds4.dll

  3. Paste them into either:

    • \Winnt\system32

    • iPlanet Directory Server install directory: [server_root]\bin\sldap\server


Setting the iPlanet Directory Server to Use the DES Algorithm
The DES algorithm is needed to encrypt the attribute where the digest password is stored.

To set the iPlanet Directory Server to use the DES algorithm, perform the following steps:

  1. Launch the iPlanet Directory Server Console.

  2. Open your iDS 5.0 instance.

  3. Select the Configuration tab.

  4. Click on the + sign next to plug-ins.

  5. Select the DES plug-in.

  6. Choose Add to add a new attribute.

  7. Enter iplanetReversiblePassword.

  8. Click Save.

  9. Restart your iPlanet Directory Server instance.
    Note In order to set a digest authentication password in the iplanetReversiblePassword attribute for a user, your entry must include the iplanetReversiblePasswordobject object.



Other Authentication

You can create a custom authentication method using the access control API.


Setting Access Control for Host-IP

You can limit access to the Administration Server, or the files and directories on your web site by making them available only to clients using specific computers. You specify hostnames or IP addresses for the computers that you want to allow or deny. You can use wildcard patterns to specify multiple computers or entire networks. Access to a file or directory using Host-IP authentication appears seamless to the user. Users can access the files and directories immediately without entering a username or password.

Since more than one person may use a particular computer, Host-IP authentication is more effective when combined with User-Group authentication. If both methods of authentication are used, a username and password will be required for access.

Host-IP authentication does not require DNS to be configured on your server. If you choose to use Host-IP authentication, you must have DNS running in your network and your server must be configured to use it. You can enable DNS on your server through the Performance Tuning page in the Preferences tab on your Server Manager.

Enabling DNS degrades the performance of iPlanet Web Server since the server is forced to do DNS look-ups. To reduce the effects of DNS look-ups on your server's performance, resolve IP addresses only for access control and CGI instead of resolving the IP address for every request. To do this, iponly=1 to AddLog fn="flex-log" name="access" in your obj.conf file:

AddLog fn="flex-log" name="access" iponly=1


Using Access Control Files

When you use access control on the Administration Server or the files or directories on your web site, the settings are stored in a file with the extension .acl. Access control files are stored in the directory server_install/httpacl with server_install being the location where the server is installed. For example, if you installed the server in /usr/iPlanet/Servers, the ACL files for both the Administration Server and each server instance configured on your server would be located in /usr/iPlanet/Servers/httpacl/.

The main ACL file name is generated-https-server-id.acl; the temporary working file is called genwork-https-server-id.acl. If you use iPlanet Administration Server to configure access, you'll have these two files. However, if you want more complex restrictions, you can create multiple files, and reference them from the server.xml file. There are also a few features available only by editing the files such as restricting access to the server based on the time of day or day of the week.

You can also manually create and edit .acl files to customize access control using APIs. For more information on using access control APIs, see the Programmer's Guide.

For more information on access control files and their syntax, see ACL File Syntax.


Configuring the ACL User Cache

By default, the iPlanet Web Server caches user and group authentication results in the ACL user cache. You can control the amount of time that ACL user cache is valid by using the ACLCacheLifetime directive in the magnus.conf file. Each time an entry in the cache is referenced, its age is calculated and checked against ACLCacheLifetime. The entry is not used if its age is greater than or equal to the ACLCacheLifetime. The default value is 120 seconds. Setting the value to 0 (zero) turns the cache off. If you use a large number for this value, you may need to restart iPlanet Web Server every time you make changes to the LDAP entries. For example, if this value is set to 120 seconds, iPlanet Web Server might be out of sync with the LDAP directory for as long as two minutes. Only set a large value if your LDAP directory is not likely to change often.

Using the magnus.conf parameter of ACLUserCacheSize, you can configure the maximum number of entries that can be held in the cache. The default value for this parameter is 200. New entries are added to the head of the list, and entries at the end of this list are recycled to make new entries when the cache reaches its maximum size.

You can also set the maximum number of group memberships that can be cached per user entry using the magnus.conf parameter, ACLGroupCacheSize. The default value for this parameter is 4. Unfortunately non-membership of a user in a group is not cached, and will result in several LDAP directory accesses on every request.

For more information on ACL file directives, see the NSAPI Programmer's Guide.



How Access Control Works


When the server gets a request for a page, the server uses the rules in the ACL file to determine if it should grant access or not. The rules can reference the hostname or IP address of the computer sending the request. The rules can also reference users and groups stored in the LDAP directory.

For example, the following ACL file contains the two default entries for the Administration Server (admin-serv), plus an additional entry that allows users in the "admin-reduced" group to access the Preferences tab in the Administration Server.

version 3.0;
# The following "es-internal" rules protect files such
# as icons and images related to iPlanet Web Server.
# These "es-internal" rules should not be modified.
  acl "es-internal";
  allow (read, list, execute,info) user = "anyone";
  deny (write, delete) user = "anyone";
# The following "default" rules apply to the entire document
# directory of iPlanet Web Server. In this example, the rules
# are set up so that "all" users in the directory server are
# allowed to read, execute, list, and get information.
# The "all" users are not allowed to write to or delete any files.
# All clients that accesses the document directory of the web
# server will be required to submit a username and password
# since this example is using the "basic" method of
# authentication. A client must be in the directory server
# to gain access to this default directory since "anyone"
# not in the directory server is denied, and "all" in the
# directory server are allowed.
  acl "default";
  authenticate (user,group) {
     database = "default";
     method = "basic";
  };
  deny (all)
  (user = "anyone");
  allow (read,execute,list,info)
  (user = "all");
# The following rules deny access to the directory "web"
# to everyone not in the directory server and deny everyone
# in the directory server who is not in GroupB.
# Only the users in GroupB are allowed read, execute, list,
# and info permissions. GroupA can not gain access to the
# directory "web" even though (in the ACL rule below) they
# can access the directory "my_stuff". Furthermore, members
# of GroupB can not write or delete files.
  acl "path=/export/user/990628.1/docs/my_stuff/web/";
  authenticate (user,group) {
     database = "default";
     method = "basic";
  };
  deny (all)
  (user = "anyone");

  allow (read,execute,list,info)
  (group = "GroupB");

# The following rule denies everyone not in the directory
# server and denies everyone in the directory server except
# user with the ID of "SpecificMemberOfGroupB". The ACL rule
# in this setting also has a requirement that the user
# connect from a specific IP address. The IP address setting
# in the rule is optional; it has been added to for extra
# security. Also, this ACl rule has a Customized prompt
# of "Presentation Owner". This Customized prompt appears
# in the username and password dialog box in the client's
# browser.

  acl "path=/export/user/990628.1/docs/my_stuff/web/presentation.html" ;
  authenticate (user,group) {
     database = "default";
     method = "basic";
     prompt = "Presentation Owner";
  };
  deny (all)
  (user = "anyone" or group = "my_group");
  allow (all)
  (user = "SpecificMemberOfGroupB") and
  (ip = "208.12.54.76");

# The following ACL rule denies everyone not in the directory
# server and everyone in the directory server except for
# GroupA and GroupB access to the directory "my_stuff"
  acl "path=/export/user/990628.1/docs/my_stuff/";
  authenticate (user,group) {
     database = "default";
     method = "basic";
  };
  deny (all)
  (user = "anyone");
  allow (read,execute,list,info)
  (group = "GroupA,GroupB");

For example, if a user requests the URL: http://server_name/my_stuff/web/presentation.html

iPlanet Web Server would first check access control for the entire server. If the ACL for the entire server was set to continue, the server would check for an ACL for the directory my_stuff. If an ACL exists, the server checks the ACEs within the ACL, and then moves on to the next directory. This process continues until an ACL is found that denies access, or until the final ACL for the requested URL (in this case, the file presentation.html) is reached.

To set up access control for this example using the Server Manager, you could create an ACL for the file only, or for each resource leading to the file. That is, one for the entire server, one for the my_stuff directory, one for the my_stuff/web directory, and one for the file.



Setting Access Control


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.

You can set access control globally for all servers through the Administration Server. Each option is described in detail in the following section, Selecting the Access Control Options.

Note Distributed administration must be configured and activated before global access control can be created.



Setting Access Control Globally

To create or edit access control globally for all servers, perform the following steps:

  1. Access the Administration Server and choose the Global Settings tab.

  2. Click the Restrict Access link.

  3. Select the administration server (https-admserv) from the drop-down list.

  4. Click either:

    • Create ACL

    • Edit ACL.

    The Access Control Rules for uri=/https-admserv/bin/* page appears:

Figure 8-2    Access Control Rules Page.

The Administration Server has two lines of default access control rules which cannot be edited.

  1. Check Access control is on, if not already selected.

  2. To create or edit the global ACL, click on Deny in the Action column.

    The Allow /Deny page is displayed in the lower frame:

Figure 8-3    Allow /Deny Page

  1. Select Allow, if it isn't already selected as the default, and click Update.

  2. Click on anyone in the Users/Groups column.

    The User/Group page appears in the lower frame:

Figure 8-4    User/Group Page

  1. Select which users and groups you will allow access to and click Update.

    Clicking List for Group and User will provide lists for you to choose from.

  2. Click on anyplace in the From Host column.

  3. Enter Host Names and IP Addresses allowed access and click Update.

  4. Click on all programs in the Programs column.

Figure 8-5    Programs

  1. Select the Program Groups or enter the specific file name in the Program Items field you will allow access to, and click Update.

  2. (Optional) Click the x under the Extra column to add a customized ACL expression.

  3. Put a check in the Continue column, if it isn't already selected as the default.

    The server will evaluate the next line before determining if the user is allowed access. When creating multiple lines, work from the most general restrictions to the most specific ones.

  4. (Optional) Click Response when denied to direct the user to a different URL or URI.

  5. Enter the path to the absolute URL or a relative URI and click update.

  6. Click Submit to store the new access control rules in the ACL file.
    Note Clicking Revert will remove all of the settings you've just created.



Setting Access Control for a Server Instance

You can create, edit, or delete access control for a specific server instance using the Server Manager.

Note If 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:

  1. Access the Server Manager and select the server instance you wish to create or edit ACLs for.

  2. Choose the Preferences tab from the Server Manager.

  3. Click the Restrict Access link.

  4. Under 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 offering three options appears:

Figure 8-6    Access Control List Management Page

  1. 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 obj.conf if you want to apply named ACLs to resources.

Table 8-2 describes the resource wildcards you can use.


Table 8-2    Server Resource Wildcards

Resource wildcard

What it means

default  

A named ACL created during installation that restricts write access so only users in the LDAP directory can publish documents.  

Entire Server  

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.  

/usr/iplanet/server4/docs/cgi-bin/*  

Controls access to all files and directories in the cgi-bin directory. You must specify an absolute path. On NT, the path must include the drive letter.  

uri="/sales"  

Controls access to the sales directory in the document root. To specify URIs, create a named ACL.  

  1. Click Edit Access Control.

    The Access Control Rules for: (server instance) appears.

Figure 8-7    Access Control Rules Page

  1. Check Access control is on, if not already selected.

  2. To create or edit the ACL for this server instance, click on Deny in the Action column.

    The Allow /Deny page is displayed in the lower frame:

Figure 8-8    Allow /Deny Page

  1. Select Allow, if it isn't already selected as the default, and click Update.

  2. Click on anyone in the Users/Groups column.

    The User/Group page appears in the lower frame:

Figure 8-9    User/Group Page

  1. Select which users and groups you will allow access to and click Update.

    Clicking List for Group and User will provide lists for you to choose from.

  2. Click on anyplace in the From Host column.

  3. Enter Host Names and IP Addresses allowed access and click Update.

  4. Click on all in the Rights column.

Figure 8-10    Access Rights Page

  1. Select one of the following and then click Update:

    • All Access Rights

    • Only the following rights and check all appropriate rights for this user

  2. (Optional) Click the x under the Extra column to add a customized ACL expression.

  3. Put a check in the Continue column, if it isn't already selected as the default.

    The server will evaluate the next line before determining if the user is allowed access. When creating multiple lines, work from the most general restrictions to the most specific ones.

  4. (Optional) Click Response when denied to direct the user to a different URL or URI.

  5. Enter the path to the absolute URL or a relative URI and click update.

  6. Click Submit to store the new access control rules in the ACL file.
    Note Clicking Revert will remove all of the settings you've just created.


  7. Repeat all steps above for each server instance you wish to establish access control for.

  8. When finished, click Apply.

  9. Select hard start /restart or dynamically apply.

ACL settings can also be enabled on a per virtual server basis. To learn how this is done, see . Editing Access Control Lists for Virtual Servers.



Selecting Access Control Options


The following sections describe the various options that you can select when setting access control. For the Administration Server, the first two lines are set as defaults, and cannot be edited.


Setting the Action

You can specify the action the server takes when a request matches the access control rule.

  • Allow means users or systems can access the requested resource

  • Deny means users or systems cannot access the resource

The server goes through the list of access control expressions (ACEs) to determine the access permissions. For example, the first ACE is usually to deny everyone. If the first ACE is set to "continue," the server checks the second ACE in the list, and if it matches, the next ACE is used. If continue is not checked, everyone would be denied access to the resource. The server continues down the list until it reaches either an ACE that doesn't match, or that matches but is set to not continue. The last matching ACE determines if access is allowed or denied.


Specifying Users and Groups

With user and group authentication, users are prompted to enter a username and password before they can access the resource specified in the access control rule.

iPlanet Web Server checks lists of users and groups stored in an LDAP server, such as iPlanet Directory Server.

You can allow or deny access to everyone in the database, you can allow or deny specific people by using wildcard patterns, or you can select who to allow or deny from lists of users and groups.

  • Anyone (No Authentication) is the default and means anyone can access the resource without having to enter a username or password. However, the user might be denied access based on other settings, such as host name or IP address. For the Administration Server, this means that anyone in the administrators group that you specified with distributed administration can access the pages.

  • Authenticated people only

    • All in the authentication database matches any user who has an entry in the database.

    • Only the following people lets you specify which users and groups to match. You can list users or groups of users individually by separating the entries with commas, or with a wildcard pattern, or you can select from the lists of users and groups stored in the database. Group matches all users in the groups you specify. User matches the individual users you specify. For the Administration Server, the users must also be in the administrators group you specified for distributed administration.

  • Prompt for authentication allows you to enter message text that appears in the authentication dialog box. You can use this text to describe what the user needs to enter. Depending on the operating system, the user will see about the first 40 characters of the prompt. Netscape Navigator and Netscape Communicator cache the username and password, and associate them with the prompt text. When the user accesses files and directories of the server having the same prompt, the usernames and passwords won't need to be entered again. If you want users to authenticate again for specific files and directories, you simply need to change the prompt for the ACL on that resource.

  • Authentication Methods specifies the method the server uses for getting authentication information from the client. The Administration server offers only the Basic method of authentication.

    • Default uses the default method you specify in the obj.conf file, or "Basic" if there is no setting in obj.conf. If you check Default, the ACL rule doesn't specify a method in the ACL file. Choosing Default allows you to easily change the methods for all ACLs by editing one line in the obj.conf file.

    • Basic uses the HTTP method to get authentication information from the client. The username and password are only encrypted if encryption is turned on for the server.

    • SSL uses the client certificate to authenticate the user. To use this method, SSL must be turned on for the server. When encryption is on, you can combine Basic and SSL methods.

    • Digest uses the an authentication mechanism that provides a way for a browser to authenticate based on username and password without sending the username and password as cleartext. The browser uses the MD5 algorithm to create a digest value using the user's password and some information provided by the Web Server. This digest value is also computed on the server side using the Digest Authentication plug-in and compared against the digest value provided by the client.

    • Other uses a custom method you create using the access control API.

  • Authentication Database lets you select a database the server will use to authenticate users. This option is only available through the Server Manager. If you choose Default, the server looks for users and groups in an LDAP directory. If you wish configure individual ACLs to use different databases, select Other, and choose the database from the drop-down list. Non-default databases and LDAP directories need to have been specified in the file server_root/userdb/dbswitch.conf. If you use the access control API for a custom database, such as Oracle or Informix, select Other, and enter the database name.


Specifying the From Host

You can restrict access to the Administration Server or your web site based on which computer the request comes from.

  • Anyplace allows access to all users and systems

  • Only from allows you to restrict access to specific Host Names or IP Addresses

If you select the Only from option, enter a wildcard pattern or a comma-separated list in the Host Names or IP Addresses fields. Restricting by hostname is more flexible than by IP address: if a user's IP address changes, you won't need to update this list. Restricting by IP address, however, is more reliable: if a DNS lookup fails for a connected client, hostname restriction cannot be used.

You can only use the * wildcard notation for wildcard patterns that match the computers' host names or IP addresses. For example, to allow or deny all computers in a specific domain, you would enter a wildcard pattern that matches all hosts from that domain, such as *.iplanet.com. You can set different hostnames and IP addresses for superusers accessing the Administration Server.

For hostnames, the * must replace an entire component of the name. That is, *.iplanet.com is acceptable, but *users.iplanet.com is not. When the * appears in a hostname, it must be the left-most character. For example, *.iplanet.com is acceptable, but users.*.com is not.

For the IP address, the * must replace an entire byte in the address. For example, 198.95.251.* is acceptable, but 198.95.251.3* is not. When the * appears in an IP address, it must be the right-most character. For example, 198.* is acceptable, but not 198.*.251.30.


Restricting Access to Programs

Access to programs can only be restricted by the Administration Server. Restricting access to programs allows only specified users to view the Server Manager pages and determines if they can configure that server. For example, you might allow some administrators to configure the Users & Groups section of the administration server and not allow them access to the Global Settings.

  • All Programs allows or denies access to all programs. By default administrators have access to all programs for a server.

  • Only the following Program Groups allows you to specify which programs the user has access to. Select the program from the drop-down list. You can choose multiple program groups by pressing the Control key while clicking on the groups. You can restrict access to the following programs groups:

    • None (default)

    • Servers

    • Preferences

    • Global Settings

    • Users & Groups

    • Security

    • Cluster Mgmt

    The Program Groups listed reflect the tabs of the Administration Server, for example, Preferences and Global Settings, and represent access to those pages. When an administrator accesses the Administration Server, the server uses their username, host, and IP to determine what pages they can view.

  • Program Items allows you to enter a page name in the Program Items field to control access to a specific page within a program.

    To determine the name of a page, place your pointer over the link in the left frame of the Administration Server and then view the text in the status bar on the bottom of your browser. The last word after the last %2b is the name for that page.

    For example, if you want the person who administers an iPlanet Directory Server to have access only to the "Configure Directory Service" page, you would set up a rule that applies only to them (host, IP, and so on), and enter dsconfig in the Program Items field

Figure 8-11    Page Name /Program Item


Setting Access Rights

Access rights can only be set by the Server Manager for a server instance. Access rights restrict access to files and directories on your web site. In addition to allowing or denying all access rights, you can specify a rule that allows or denies partial access rights. For example, you allow users read-only access rights to your files, so they can view the information, but not change the files.

  • All Access Rights is the default and will allow or deny all rights

  • Only the following rights allows you to select a particular combination of rights to be allowed or denied

    • Read allows users to view files, including includes the HTTP methods GET, HEAD, POST, and INDEX

    • Write allows users to change or delete files, including the HTTP methods PUT, DELETE, MKDIR, RMDIR, and MOVE. To delete a file, a user must have both write and delete rights

    • Execute allows users to execute server-side applications, such as CGI programs, Java applets, and agents

    • Delete allows users who also have write privileges to delete files or directories.

    • List allows users to access lists of the files in directories that don't contain an index.html file.

    • Info allows users to receive information about the URI, for example http_head.


Writing Customized Expressions

You can enter custom expressions for an ACL. Only select this option if you are familiar with the syntax and structure of ACL files. There are a few features available only by editing the ACL file or creating custom expressions. For example, you can restrict access to your server depending on the time of day, day of the week, or both.

The following customized expression shows how you could restrict access by time of day and day of the week. This example assumes you have two groups in your LDAP directory: the "regular" group gets access Monday through Friday, 8:00am to 5:00pm. The "critical" group gets access all the time.

allow (read)
{
   (group=regular and dayofweek="mon,tue,wed,thu,fri");
   (group=regular and (timeofday>=0800 and timeofday<=1700));
   (group=critical)
}

For more information on valid syntax and ACL files, see ACL File Syntax and Referencing ACL Files in obj.conf.


Turning Off Access Control

When you uncheck the option labeled "Access control is on," you'll get a prompt asking if you want to erase records in the ACL. When you click OK, the server deletes the ACL entry for that resource from the ACL file.

If you want to deactivate an ACL, you can comment out the ACL lines in the file generated-https-server-id.acl by putting # signs at the beginning of each line.

From the Administration Server, you could create and turn on access control for a specific server instance and leave it off (which is the default) for other servers. For example, you could deny all access to the Server Manager pages from the Administration Server. With distributed administration on and access control off by default for any other servers, administrators could still access and configure the other servers, but they cannot configure the Administration Server.


Note This access control is in addition to the user being in the administrators group set for distributed administration. The Administration Server first checks that a user (other than superuser) is in the administrators group, and then evaluates the access control rules.



Responding When Access is Denied

iPlanet Web Server provides the following default message when access is denied: "FORBIDDEN. Your client is not allowed access to the restricted object." You can choose a different response when denied access. You can also create a different message for each access control object.

To change the message sent for a particular ACL, perform the following steps:

  1. Click the Response when denied link in the ACL page.

  2. Check Respond with the following file in the lower frame.

  3. Enter the path to the absolute URL or a relative URI and click update.

    Make sure users have access to the URL or URI they are redirected to.

  4. Click Update.

  5. Click Submit in the top frame to submit the access control rule.



Limiting Access to Areas of Your Server

This section describes some commonly used access restrictions to a web server and its contents. The steps for each procedure detail the specific actions you need to take; however, you will still need to complete all of the steps described under Setting Access Control for a Server Instance.

The following procedures are described in this section:


Restricting Access to the Entire Server

You may wish to allow access to users in a group called who access the server from computers in a subdomain. For instance, you may have a server for a company department that you only want users to access from computers in a specific subdomain of your network.

Using the steps described for setting access control for a server instance, you would:

  1. Use the Server Manager to select the server instance.

  2. Choose the Preferences tab.

  3. Click the Restrict Access link.

  4. Choose the ACL File to edit.

  5. Pick the entire server resource, and click Edit Access Control.

  6. Add a new rule to deny access to all.

  7. Add another new rule to allow access to a specific group.

  8. Enter a wildcard pattern for the host names of the computers to be allowed.

    For example, *.employee.iplanet.com

  9. Unselect Continue.

  10. Submit and Apply your changes.


Restricting Access to a Directory (Path)

You can allow users in a group to read or run applications in directories, and its subdirectories and files, that are controlled by an owner of the group. For example, a project manager might update status information for a project team to review.

To limit access to a directory on the server, using the steps described for setting access control for a server instance, you would:

  1. Use the Server Manager to select the server instance.

  2. Choose the Preferences tab.

  3. Click the Restrict Access link.

  4. Choose the ACL File to edit.

  5. Browse the Pick a Resource section and select the directory you want to restrict.

    The directories in the server's document root are displayed. Once selected, the Editing drop-down list displays the absolute path to the directory.


    Note

    If you want to view all files in your server root, click Options and then check List files as well as directories.


  6. Click Edit Access Control.

  7. Create a new rule and leave the defaults to deny access to everyone from everywhere.

  8. Create another new rule allowing users in a specific group to have read and execute rights only.

  9. Create a third line to allow a specific user to have all rights.

  10. Unselect Continue for the second and third lines and click Update.

  11. Submit and Apply your changes.

An absolute path to the file or directory would be created in the docroot directory. The entry in the ACL file would appear as follows: acl "path=d:\iPlanet\suitespot\docroot1\sales/";


Restricting Access to a URI (Path)

You can use a URI to control access to a single user's content on the web server. URIs are paths and files relative to the server's document root directory. Using URIs is an easy way to manage your server's content if you frequently rename or move all or part of it (for example, for disk space). It's also a good way to handle access control if you have additional document roots.

To limit access to a URI, using the steps described for setting access control for a server instance, you would:

  1. Use the Server Manager to select the server instance.

  2. Choose the Preferences tab.

  3. Click the Restrict Access link.

  4. Enter the URI you want to restrict in the Type in the ACL name section.

    For example: uri=/my_directory.

  5. Click Edit Access Control.

  6. Create a new rule to allows all users read access.

  7. Create another new rule to allow access for the owner of the directory.

  8. Uncheck Continue for both the first and second rules.

  9. Click Submit and Apply your changes.

A path for the URI is created relative to the document root. The entry in the ACL file would appear as follows: acl "uri=/my_directory";


Restricting Access to a File Type

You can limit access to file types on your server or web site. For example, you might wish to allow only specific users to create programs that run on your server. Anyone would be able to run the programs, but only specified users in the group would be able create or delete them.

To limit access to a file type, using the steps described for setting access control for a server instance, you would:

  1. Use the Server Manager to select the server instance.

  2. Choose the Preferences tab.

  3. Click the Restrict Access link.

  4. Click Wildcard in the Pick a resource section and enter a wildcard pattern.

    For example, *.cgi.

  5. Click Edit Access Control.

  6. Create a new rule to allow read access to all users.

  7. Create another rule that allows write and delete access only to a specified group.

  8. Submit and Apply your changes.

For file type restriction, you would leave both continue boxes checked. If a request for a file comes in, the server will then check the ACL for the file type first.

A Pathcheck function is created in obj.conf that may include wildcard patterns for files or directories. The entry in the ACL file would appear as follows: acl "*.cgi";


Restricting Access Based on Time of Day

You can restrict write and delete access to the server or during specified hours or on specified days. You might use this to prevent people from publishing documents during working hours when people might be accessing the files.

To limit access based on time of day, using the steps described for setting access control for a server instance, you would:

  1. Use the Server Manager to select the server instance.

  2. Choose the Preferences tab.

  3. Click the Restrict Access link.

  4. Select the entire server from the drop-down list in Pick a Resource and click Edit Access Control.

  5. Create a new rule allowing read and execute rights to all.

    This means that if a user wants to add, update, or delete a file or directory, this rule won't apply and the server will search for another rule that matches.

  6. Create another new rule denying write and delete rights to all.

  7. Click X link to create a customized expression.

  8. Enter the days of the week and the times of day to be allowed.

    Example:
    user = "anyone" and
    dayofweek = "sat,sun" or
    (timeofday >= 1800 and
    timeofday <= 600)

    The message "Unrecognized expressions" will be displayed in the Users/Groups and From Host fields when you create a custom expression.

  9. Submit and Apply your changes.

Any errors in the custom expression will generate an error message. Make corrections and submit again.


Restricting Access Based on Security

As of iPlanet Web Server 6.0 you can configure SSL and non-SSL listen sockets for the same server instance. Restricting access based on security allows you to create protection for resources that should only be transmitted over a secure channel.

To limit access based on security, using the steps described for setting access control for a server instance, you would:

  1. Use the Server Manager to select the server instance.

  2. Choose the Preferences tab.

  3. Click the Restrict Access link.

  4. Select the entire server from the drop-down list in Pick a Resource and click Edit Access Control.

  5. Create a new rule allowing read and execute rights to all.

    This means that if a user wants to add, update, or delete a file or directory, this rule won't apply and the server will search for another rule that matches.

  6. Create another new rule denying write and delete rights to all.

  7. Click X link to create a customized expression.

  8. Enter ssl="on".

    Example:
    user = "anyone" and ssl="on"

  9. Submit and Apply your changes.

Any errors in the custom expression will generate an error message. Make corrections and submit again.



Working with Dynamic Access Control Files


Server content is seldom managed entirely by one person. You may need to allow end users to access a subset of configuration options so that they can configure what they need to, without giving them access to the iPlanet Web Server. The subset of configuration options are stored in dynamic configuration files.

The following topics are described in this section:


Using .htaccess Files

iPlanet Web Server supports.htaccess dynamic configuration files. You can enable .htaccess files either through the user interface or by manually changing the configuration files. The files that support .htaccess are in the server_root/plugins/htaccess directory. These files include a plug-in that enables you to use .htaccess files and a script for converting .nsconfig files to .htaccess files.

You can use .htaccess files in combination with the server's standard access control. The standard access controls are always applied before any .htaccess access control, regardless of the ordering of PathCheck directives. Do not require user authentication with both standard and .htaccess access control when user-group authentication is `Basic' You could use SSL client authentication via the standard server access control, and also require HTTP `Basic' authentication via an .htaccess file.

This section includes the following topics:


Enabling .htaccess from the User Interface

To configure your iPlanet Web Server to use .htaccess, perform the following steps:

  1. Access the Server Manager and select the server instance you wish to enable .htaccess for.

  2. Click on the Class Manager link at the top of the screen.

  3. Select the Content Mgmt tab.

  4. Click on the .htaccess Configuration link.

  5. Select the server to edit by:

    • Choosing the entire server or a specific server from the drop-down list

    • Choosing the directory and files to edit by clicking Browse

    • Choosing a wildcard pattern to edit by clicking Wildcard

  6. Select Yes to activate .htaccess.

  7. Enter the file name where you want the .htaccess configuration to be added.

  8. Click OK.

  9. When finished, click Apply.

  10. Select hard start /restart or dynamically apply.


Enabling .htaccess from magnus.conf

To manually enable your sever to use the .htaccess, you need to first modify the server's magnus.conf file to load, initialize, and activate the plug-in.

  1. Open magnus.conf in the server_root/https-server_name/config file.

  2. After the other Init directives, add the following lines:

    • For Unix/Linux:

      Init fn="load-modules" funcs="htaccess-init,htaccess-find"
      shlib="      server_root/plugins/htaccess/htaccess.so" NativeThread="no"
      Init fn="htaccess-init"

    • For Windows NT:

      Init fn="load-modules" funcs="htaccess-init,htaccess-find,htaccess-register"
      shlib="      server_root/plugins/htaccess/htaccess.dll" NativeThread="no"
      Init fn="htaccess-init"

    • For HP:

      Initfn="load-modules" funcs="htaccess-init,htaccess-find,htaccess-register" shlib="<server_root>/plugins/htaccess/htaccess.sl" NativeThread="no"

      Init fn="htaccess-init"

  3. (Optional) Make the final line read:

    Init fn="htaccess-init"[groups-with-users=yes]

  4. Click File /Save.

  5. Open obj.conf.

  6. Add the PathCheck directive as the last directive in the object.

    1. To activate .htaccess file processing for all directories managed by a virtual server, add the PathCheck directive to the default object in the object.conf file:

      <Object name="default">

      ...

    PathCheck fn="htaccess-find"

    </Object>

    .htaccess processing should be the last PathCheck directive in the object.

    1. To activate .htaccess file processing for particular server directories, place the PathCheck directive in the corresponding definition in magnus.conf.

  7. To name your .htaccess files something other than .htaccess, you must specify the filename in the PathCheck directive using the following format:

    PathCheck fn="htaccess-find" filename="filename"
    Note The next time you use the Administration Server, you will be warned that manual edits have been applied. Click Apply to accept your changes.


Subsequent access to the server will be subject to .htaccess access control in the specified directories. For example, to restrict write access to .htaccess files, create a configuration style for them, and apply access control to that configuration style. For more information, see Applying Configuration Styles


Converting Existing .nsconfig Files to .htaccess Files

iPlanet Web Server 6.0 includes the htconvert plug-in for converting your existing .nsconfig files to .htaccess files. The .nsconfig files are no longer supported. If you have been using.nsconfig files, you should convert them to .htaccess files.

When activated, htconvert searches the given server.xml files for pfx2dir and document-root directives. Each .nsconfig file found will be translated into an .htaccess file. Multiple obj.conf files can be converted depending on configuration.

Note If there is an existing .htaccess file, htconvert will produce an .htaccess.new file, and give a warning. If .htaccess and .htaccess.new already exist, the new file will be named .htaccess.new.new. The.new will be repeatedly appended.


The htconvert plug-in currently only supports the RestrictAccess and RequireAuth directives, and the <Files> wrapper. If <Files> other than <Files*> are presented, the script will give a warning and behave as though all files in the directory are to be access-controlled.

To convert your files, at the command prompt, enter the path to Perl on your system, the path to the plug-in script, and the path to your server.xml file. For example:

server_root\install\perl server_root/plugins/htaccess/htconvert server_root/https-server_name/config/server.xml

All .nsconfig files are converted to .htaccess files, but not deleted.

The groups-with-users option facilitates handling large numbers of users in groups. If you have many users in a group, follow these steps:

  1. Revise the format of the user file format to list all the groups a user belongs to:

    username:password:group1,group2,group3,...groupn

  2. Revise the AuthGroupFile directive to point to the same file as the AuthUserFile.

Alternatively, you can:

  1. Remove the AuthGroupFile directive entirely.

  2. Add the following to the Init fn=htaccess-init line in the magnus.conf file:

    groups-with-users="yes"


Using htaccess-register

The htaccess-register is a new function allowing you to create your own authentication methods. Like Apache you can create external authentication modules and plug them into the .htaccess module via htaccess-register. Two sample modules are provided in server_root/plugins/nsapi/htaccess.

You can use external modules to create one or more new directives. For example, you might specify the user database for authentication. The directives may not appear within <Limit> or <LimitExcept> tags.


Example of an .htaccess File

The following example shows an .htaccess file:
<Limit> GET POST
order deny,allow
deny from all
allow from all
</Limit>
<Limit> PUT DELETE
order deny,allow
deny from all
</Limit>
AuthName mxyzptlk.kawaii.com
AuthUserFile /server_root/mxyz-docs/service.pwd
AuthGroupFile /server_root/mxyz-docs/service.grp


Supported .htaccess Directives

The following .htaccess directives are supported in this release:


allow


Syntax
Allows from host where:

  • host is all, to allow access from all client hosts

  • host is all or the last part of a DNS host name

  • host is a full or partial IP address

Does not need to be enclosed within a <Limit> or <LimitExcept> range but usually is.


Effect
Allows access to the specified hosts. Normally appears inside a <Limit> range.


deny


Syntax
Deny from host where:

  • host is all, to deny access from all client hosts

  • host is all or the last part of a DNS host name

  • host is a full or partial IP address

Does not need to be enclosed in a <Limit> <LimitExcept> range but usually is.


Effect
Denies access to the specified hosts. Normally appears inside a <Limit> range.


AuthGroupFile


Syntax
AuthGroupFile filename where filename is the name of file containing group definitions in the form: groupname: user user.

Must not appear within a <Limit> or <LimitExcept> range.


Effect
Specifies that the named group file is to be used for any group definitions referenced in a require group directive. Note that if the filename specified in an AuthGroupFile directive is the same as the filename in an AuthUserFile directive, the file is assumed to contain users and groups in the format:

username:DES-encrypted-password:comma-separated-list-of-groups


AuthUserFile


Syntax
AuthUserFile filename where:

  • filename is the name of file containing user definitions in the form: username:password

  • username is a user login name, and password is the DES-encrypted password.

Must not appear within a <Limit> or <LimitExcept> range.


Effect
Specifies that the named user file is to be used for any user names referenced in a require user or require valid-user directive.

Note that the use of groups-with-users=yes in the Init fn=htaccess-init directive in obj.conf, or specifying an AuthGroupFile directive with the same filename, causes that file to be assumed to be in the format:

username:DES-encrypted-password:comma-separated-list-of-groups


AuthName


Syntax
AuthName authentication realm where authentication realm is a string identifying an authorization realm to be associated with any request for user authentication.

Must not appear within a <Limit> or <LimitExcept> range.


Effect
The authentication realm string typically appears in the prompt for username and password on the client side. It may affect caching of username and password on the client.


AuthType


Syntax
AuthType Basic. Must not appear within a <Limit> or <LimitExcept> range.


Effect
Specifies the user authentication method as HTTP Basic Authentication, the only method currently supported.


<Limit>


Syntax
<Limit method method ...>

allow, deny, order, or require directives

</Limit>

where method is an HTTP method such as GET, POST, or PUT. Any method that the web server understands can be used here.


Effect
Applies the enclosed directives only for requests using the specified HTTP methods.


<LimitExcept>


Syntax
<LimitExcept method method ...>

allow, deny, order, or require directives

</LimitExcept>

where method is an HTTP method such as GET, POST, or PUT. Any method that the web server understands can be used here.


Effect
Applies the enclosed directives only for requests types not matching the specified HTTP methods.


order


Syntax
Order ordering where ordering is one of:

  • allow, deny

  • deny, allow

  • mutual-failure

Does not need to be enclosed within a <Limit> or <LimitExcept> range, but usually is.


Effect

  • allows, denies, evaluates allow directives and then deny directives

  • denies, allows, evaluates deny directives and then allow directives

  • mutual-failure denies access for a host listed in both allow and deny directives, regardless of their ordering


require


Syntax

  • requires group groupname groupname

  • requires user username username

  • requires valid-user

Does not need to be enclosed within a <Limit> or <LimitExcept> range, but usually is.


Effect

  • requires group requires the authenticated user to be a member of one of the specified groups.

  • requires user requires the authenticated user to be one of the specified users.

  • requires valid-user requires an authenticated user


.htaccess Security Considerations

By default, server support for HTTP PUT is disabled. You can activate HTTP PUT using the Remote File Manipulation page of Content Mgmt in the Class Manager. Great care should be taken in allowing PUT access to directories containing .htaccess files, since it will allow them to be replaced. PUT access can be prevented on all files in a directory by restricting access. See Restricting Access to a Directory (Path) .



Controlling Access for Virtual Servers


Access control information in iPlanet Web Server 6.0 can come from a per-virtual server ACL file and .htaccess files in the document directories. The .htaccess system is unchanged from iPlanet Web Server 4.x.

Your server.xml file can contain one or more ACLFILE tags which define an ID associated to a particular standard iPlanet Web Server 6.x ACL file. For example:

<ACLFILE id="standard" file="standard.acl">

For virtual servers to use access control you must create a reference to one or more ACL file IDs in their `aclids' property. Example:

<VS aclids="standard">

This configuration allows multiple virtual servers to share the same ACL file. If you want to require user-group authentication for a virtual server, you must add one or more USERDB tags to its definition. These USERDB tags create a connection between the database names in your ACL file and the actual databases found in dbswitch.conf.

The following example maps the ACLs with no `database' attribute to the `default' database in dbswitch.conf:

<VS>

   <USERDB id="default" database="default"/>

</VS>


Accessing Databases from Virtual Servers

You can globally define user authentication databases in the dbswitch.conf file. It is only read at server startup.

The baseDN of the LDAP URL in dbswitch.conf defines the global root of all accesses to the database. This maintains backward compatibility. For most new installations, the baseDN would be empty.

dcsuffix is a new attribute for LDAP databases in dbswitch.conf that defines the root of the DC tree according to the iPlanet LDAP schema. It is relative to the baseDN in the LDAP URL. When the dcsuffix attribute is present, the LDAP database is iPlanet LDAP schema compliant, and the behaviour of some operations changes. For more information about the iPlanet LDAP schema, and an example see "The iPlanet LDAP Schema" in Chapter 8 of the NSAPI Programmer's Guide.

For every virtual server, you can define one or more USERDB blocks that point to one of the directories, and you can define additional information. The USERDB blocks ID can be referenced in the database parameter of the ACL. If a virtual server has no USERDB blocks, user or group-based ACLs will fail.

USERDB tags define an additional layer of indirection between the database attribute of an ACL and dbswitch.conf. This layer of indirection adds the necessary protection for the server administrator to have full control over which databases virtual server administrators have access to.

For more information on USERDB, see "User DB Selection" in Chapter 8 of the NSAPI Programmer's Guide.


Specifying LDAP Databases in the User Interface

After you have defined one or more user authentication databases in dbswitch.conf, you can use the Class Manager to configure which databases each of your virtual servers will use for authentication. You can also use the Class Manger to add a newly created database definition from dbswitch.conf for the virtual server to authenticate against

To specify which LDAP database or databases a virtual server should use, perform the following steps:

  1. Access the Server Manager and select the Virtual Server Class tab.

  2. Click on the virtual server class link where you wish to specify the LDAP database listed under Tree View of the Server.

  3. Select the Virtual Servers tab, if not already displayed.

  4. Click the ACL Settings link.

  5. Choose ACL Settings from the Select a Setting drop-down list.

    The ACL Settings for Virtual Servers page is displayed.

  6. Choose Edit from the drop-down list in the Option column, if not already displayed.

  7. Select a database configuration from the drop-down list in the Database column of the virtual server you are editing.

  8. Click OK.

  9. Close the Edit ACL Files window.

  10. Click Apply.

  11. Choose dynamically apply.


Editing Access Control Lists for Virtual Servers

ACLs for virtual servers are created for the server instance that the virtual server resides in. Virtual server ACL settings default to those created for the server instance. However, access control for each virtual server can be edited through the Class Manager. You would also use this method to add a newly created ACL file to a virtual server.

To edit ACL settings for a virtual server, perform the following steps:

  1. Access the Server Manager and select the Virtual Server Class tab.

  2. Click on the virtual server class link where you wish to specify the LDAP database listed under Tree View of the Server.

  3. Select the Virtual Servers tab, if not already displayed.

  4. Click the ACL Settings link.

  5. Choose Edit or Delete from the drop-down list in the Option field for each virtual server you wish to change.

  6. Click the Edit link in the ACL File field to display the available ACL files.

  7. Select one or more ACL files to add or delete for the virtual server.

    A virtual server can have multiple ACL files because they may have multiple document roots.

  8. Choose the database to associate the ACL list with from the drop-down list.

  9. (Optional) Enter the BaseDN.

  10. Click OK when you have finished making changes.

  11. Click Apply.

  12. Select dynamically apply.


Previous     Contents     Index     DocHome     Next     
Copyright © 2001 Sun Microsystems, Inc. Some preexisting portions Copyright © 2001 Netscape Communications Corp. All rights reserved.

Last Updated May 10, 2001