User manual REDHAT NETSCAPE ENTREPRISE SERVER 6.1 04-2002 ADMINISTRATOR

[. . . ] Administrator's Guide Netscape Enterprise Server Version 6. 1 April 2002 (Draft) Netscape Communications Corporation ("Netscape") and its licensors retain all ownership rights to the software programs offered by Netscape (referred to herein as "Software") and related documentation. Use of the Software and related documentation is governed by the license agreement for the Software and applicable copyright law. Your right to copy this documentation is limited by copyright law. Making unauthorized copies, adaptations or compilation works is prohibited and constitutes a punishable violation of the law. [. . . ] 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. Chapter 8 Controlling Access to Your Server 185 Selecting Access Control Options 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 *. example. 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, *. example. com is acceptable, but *users. example. com is not. When the * appears in a hostname, it must be the left-most character. For example, *. example. 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. [. . . ] TCP/IP Transmission Control Protocol/Internet Protocol. The main network protocol for the Internet and for enterprise (company) networks. telnet A protocol where two machines on the network are connected to each other and support terminal emulation for remote login. timeout A specified time after which the server should give up trying to finish a service routine that appears hung. [. . . ]