• Wildcard entries
• User, server, and group names (including user and group names of Internet clients)
• Alternate names
• LDAP users
• Anonymous, which can be used for anonymous Internet user access and anonymous Notes user access
• Database replica IDs

Add names to the ACL in the hierarchical format assigned by the IBM® Lotus® Domino(TM) server administrator. For example:

Sandra E Smith/West/Acme/US

Wildcard entries

To allow general access to a database, you can enter hierarchical names with a wildcard character (*) in the ACL. You can use wildcards in the common name and organizational unit components.

Users and/or servers who do not already have a specific user or group name entry in the ACL, and whose hierarchical names include the components that contain a wildcard, are given the highest level of access specified by every one of the wildcard entries that match.

Here is an ACL entry in wildcard format:

*/Illustration/Production/Acme/US

Mary Tsen/Illustration/Production/Acme/US

Michael Bowling/Illustration/Production/Acme/US

Sandy Braun/Documentation/Production/Acme/US

Alan Nelson/Acme/US

User names

You can add to an ACL the names of any individuals with certified IBM® Lotus® Notes® user IDs or Internet users who authenticate using name-and-password or SSL client authentication.

• For Notes users, enter the full hierarchical name for each user -- for example, John Smith/Sales/Acme -- regardless of whether the user is in the same hierarchical organization as the server that stores the database.
• For Internet users, enter the name that appears as the first entry in the User name field of the Person document. You can enter multiple alias names in the User name field, but the first entry is used to perform the security authorization check so it is the first entry that should be used on all Domino ACLs -- that is, server file and database ACLs.

For more information on setting a maximum level of access for Internet users, see Maximum Internet name-and-password access.

Server names

You can add server names to an ACL to control the changes a database receives from a database replica. To ensure tighter security, use the full hierarchical name of the server -- for example, Server1/Sales/Acme -- regardless of whether the name of the server being added is in a different hierarchical organization than that of the server that stores the database.

Group names

You can add a group name -- for example, Training -- to the ACL to represent multiple users or servers that require the same access. Users must be listed in groups with a primary hierarchical name or an alternate name. Groups can also have wildcard entries as members. Before you can use a group name in an ACL, you must create the group in the Domino Directory or in an LDAP directory that has been configured for group expansion in the Directory Assistance database.

Tip Use individual names rather than group names for the managers of a database. Then when users choose Create - Other - Memo to Database Manager, they'll know whom they are addressing.

Groups provide a convenient way to administer a database ACL. Using a group in the ACL offers the following advantages:

• You can add one group name instead of adding a long list of individual names to an ACL,. If a group is listed in more than one ACL, modify the group document in the Domino Directory or the LDAP Directory, rather than add and delete individual names in multiple databases.
• You can change the access level for several users or servers at the same time.
• You can use group names to reflect the responsibilities of group members or the organization of a department or company.

Terminations group

When employees leave an organization, the Domino administrator should remove their names from all groups in the Domino Directory and add them a terminations group, which is denied access to servers. Work with your server administrator to make sure that the names of terminated employees are removed from the ACLs of all databases in your organization. Make sure that the terminations group is added to the ACLs and that the group is assigned No Access.

You can also use the Deny Access group for this purpose. The Deny Access group contains the names of Notes users who no longer have access to Domino servers. When you delete a person from the Domino Directory, you have the option to "Add deleted user to deny access group," if such a group has been created. (If no such group exists, the dialog box displays "No Deny Access group selected or available.")

For more information on the Deny Access group, see Lotus Domino Administrator Help.

Alternate names

An alternate name is an optional alias name that an administrator assigns to a registered Notes user, often to publish a name in two different character sets, such as English and Kanji. You can add alternate names to an ACL. An alternate name provides the same level of security as the user's primary hierarchical name. An example of a user name in alternate name format is Sandy Smith/ANWest/ANSales/ANAcme, where AN is an alternate name.

LDAP users

You can use a secondary LDAP directory to authenticate Web users. You can then add the names of these Internet users to database ACLs to control user access to databases.

You can also create groups in the secondary LDAP directory that include the Internet user names and then add the groups as entries in Notes database ACLs. For example, an Internet user may try to access a database on a Domino Web server. If the Web server authenticates the user, and if the ACL contains a group named "Web," the server can look up the Web user's name in the group "Web" located in the foreign LDAP directory, in addition to searching for the entry in the primary Domino Directory. Note that for this scenario to work, the Directory Assistance database on the Web server must include an LDAP Directory Assistance document for the LDAP directory with the Group Expansion option enabled. You can also use this feature to look up the names of Notes users stored in foreign LDAP directory groups for database ACL checking.

When you add the name of an LDAP directory user or group to a database ACL, use the LDAP format for the name, but use a forward slash (/), rather than a comma (,), as a delimiter. For example, if the name of a user in the LDAP directory is:

uid=Sandra Smith,o=Acme,c=US

uid=Sandra Smith/o=Acme/c=US

cn=managers

managers

cn=managers,o=acme

cn=managers/o=acme

For example, if you enter this name in an ACL:

cn=Sandra Smith/ou=West/o=Acme/c=US

Sandra Smith/West/Acme/US

Anonymous database access is given to Internet users and to Notes users who have not authenticated with the server. You can control the level of database access granted to an anonymous user or server by entering the name Anonymous in the access control list, and assigning an appropriate level of access. Typically you assign Anonymous users Reader access to a database.

The table below describes different ways that an anonymous user can access a database:

Access specified	Anonymous access enabled for Internet protocol	Anonymous access not enabled for Internet protocol
Anonymous access enabled in database ACL	Users access the database with the Anonymous entry's access level. For example, if Anonymous access is set to Reader, anonymous users who access the database have Reader access.	Users are prompted to authenticate when they attempt to access any resource on the server. If the user is not listed in the database (through a group entry, a wildcard entry, or if the user name is explicitly listed), then the user accesses the database with the -Default- entry's access level.
Anonymous not listed in database ACL	Anonymous users access the database with the -Default- entry's access level. For example, if -Default- access is set to Reader, and there is no Anonymous entry in the ACL, anonymous users who access the database have Reader access.
Anonymous assigned "No Access" in database ACL Note "Read and write public documents" privileges should be disabled	Users will be prompted to authenticate when they attempt to access this database. When authenticated they will be granted the appropriate access level assigned in the ACL.

Anonymous users (both those who are given access to a database through the Anonymous entry and those who have access through the -Default- entry) who try to do something that is not allowed for their access level will be prompted to authenticate. For example, if Anonymous is set to Reader, and an anonymous user tries to create a new document, that user is prompted to authenticate with a name and password.

Tip If you want all users to authenticate with a database, make sure that Anonymous is in the database ACL with an access level of No Access, and add the Internet user's name to the ACL with the level of access you want the user to have. You should also be sure that the Read Public Documents and Write Public Documents privileges are not enabled in the database ACL.

The Domino server uses the group name Anonymous solely for access control checks. For example, if Anonymous has Author access in the database ACL, the true name of the user appears in the Authors field of documents the user creates in the database. The Domino server can display only the true name of anonymous Notes users, but not of anonymous Web users, in the Authors field of the document. Authors fields are never a security feature, regardless if anonymous access is used; if the validity of the author's name is needed for security, then the document should be signed.

Replica IDs

To allow an agent in one database to use @DbColumn or @DbLookup to retrieve data from another database, enter the replica ID of the database containing the agent in the ACL of the database containing the data to be retrieved. The database containing the agent must have at least Reader access to the database containing the data to be retrieved. Both databases must be on the same server. An example of a replica ID in a database ACL is 85255B42:005A8fA4.

If you do not add the replica ID to the access control list, the other database can still retrieve data if the -Default- access level of your database is Reader or higher.

To determine the replica ID of a database, choose File - Database - Properties, and click the Info (i) tab. Or choose File - Database - Design Synopsis, and select Replication.

To add a replica ID to the ACL

Type or copy and paste the replica ID from the Design Synopsis dialog box into the ACL or type the replica ID you get from the info (i) tab of the Database properties box. You can type the replica ID in uppercase or lowercase characters, but do not enclose it in quotation marks.

Order of evaluation for ACL entries

ACL entries are evaluated in a specific order to determine the access level that will be granted to an authenticated Notes user trying to access the database.

• The ACL first checks the user name to see if it matches any of the ACL entries. The ACL checks all matching user names. For example, Sandra E Smith/West/Acme would match the entries Sandra E Smith/West/Acme/US and Sandra E Smith. In the event that two different entries for an individual have different access levels (for example, applied at different times by different administrators), the user trying to access the database would be granted the highest access level, as well as the union the access privileges of the two entries for that user in the ACL. This can also happen if the user has alternate names.

  Note If you enter only the common name in the ACL (for example, Sandra E Smith), then that entry matches only if the user's name and the database server are in the same domain hierarchy. For example, if the user is Sandra E Smith, whose hierarchical name is Sandra E Smith/West/Acme, and the database server is Manufacturing/FactoryCo, then the entry Sandra E Smith will not get the correct level of access for ACLs on the server Manufacturing/FactoryCo. The name must be entered in full hierarchical format in order for the user to obtain the correct level of access to ACLs on servers in other domains.

• If no match is made on the user name, the ACL then checks to see if there is a group name entry that can be matched. If an individual trying to access the database happens to match more than one group entry -- for example, if the person is a member of Sales and the two group entries for Sales are Sales/West/Acme and Sales/Acme -- then the individual is granted the highest access level, as well as the union of the access privileges of the two entries for that group in the ACL.

  Note If the user matches an explicit entry in the ACL, and is a member of a group that is also listed in the ACL, then the user always gets the level of access assigned to the explicit entry, even if the group access level is higher.

• If no match is made on the group name, the ACL then checks to see if there is a wildcard entry that can be matched. If the individual trying to access the database happens to match more than one wildcard entry, the individual is granted the highest access level, as well as the union of the access privileges of all the wildcard entries that match.
• If a group entry and a wildcard entry both apply to a user attempting to access the database, then the user has the access assigned to the group entry. For example, if the group Sales has Reader access and the wildcard entry */west/Acme has Manager access, and both entries apply to a user, then the user has Reader access to the database.
• If no match can be made from among the database ACL entries, the individual is granted the level of access defined for the -Default- entry.

Setting up a database ACL
Default ACL entries

Glossary