Home
Securing
This section describes security features, including execution control lists, IDs, and SSL.
Name-and-password authentication for Internet/intranet clients
Name-and-password authentication, also known as basic password authentication, uses a basic challenge/response protocol to ask users for their names and passwords and then verifies the accuracy of the passwords by checking them against a secure hash of the password stored in Person documents in the Domino® Directory.
Controlling the level of authentication for Internet clients
You can select the level of restriction HCL Domino® uses when authenticating users in Domino Directories and LDAP directories, and the user has supplied a user name and password. This applies to all Internet protocols (HTTP, LDAP, IMAP, POP3).
Authenticating Internet name-and-password clients in secondary Domino® and LDAP directories
When an Internet client authenticates with a server, by default the server checks the primary HCL Domino® Directory to see if it can find a Person document with a name and password that match those entered by the Internet client. If your organization uses a secondary Domino Directory and/or an LDAP directory to verify Internet clients who use name-and-password authentication, you can set up Domino to check those additional directories. To do so, you set up the secondary Domino Directories and LDAP directories as trusted domains in the Directory Assistance database.

Securing
This section describes security features, including execution control lists, IDs, and SSL.
- Overview of Domino security
  Setting up security for your organization is a critical task. Your security infrastructure is critical for protecting your organization's IT resources and assets. As an administrator, you need to give careful consideration to your organization's security requirements before you set up any servers or users. Up-front planning pays off later in minimizing the risks of compromised security.
- Server access for Notes® users, Internet users, and Domino® servers
  To control user and server access to other servers, Domino® uses the settings you specify on the Security tab in the Server document as well as the rules of validation and authentication. If a server validates and authenticates the Notes® user, Internet user, or server, and the settings in the Server document allow access, the user or server is allowed access to the server.
- The database access control list
  Every .NSF database has an access control list (ACL) that specifies the level of access that users and servers have to that database. Although the names of access levels are the same for users and servers, those assigned to users determine the tasks that they can perform in a database, while those assigned to servers determine what information within the database the servers can replicate. Only someone with Manager access can create or modify the ACL.
- Domino® server and Notes® user IDs
  Domino® uses ID files to identify users and to control access to servers. Every Domino server, Notes® certifier, and Notes user must have an ID.
- The execution control list
  You use an execution control list (ECL) to configure workstation data security. An ECL protects user workstations against active content from unknown or suspect sources, and can be configured to limit the action of any active content that does run on workstations.
- Domino® server-based certification authority
  You can set up a Domino® certifier that uses the CA process server task to manage and process certificate requests. The CA process runs as a process on Domino servers that are used to issue certificates. When you set up a Notes® or Internet certifier, you link it to the CA process on the server in order to take advantage of CA process activities. Only one instance of the CA process can run on a server; however, the process can be linked to multiple certifiers.
- SSL security
  Secure Sockets Layer (SSL) is a security protocol that provides communications privacy and authentication for Domino® server tasks that operate over TCP/IP.
- SSL and S/MIME for clients
  Clients can use a Domino® certificate authority (CA) application or a third-party CA to obtain certificates for secure SSL and S/MIME communication.
- Encryption
  Encryption protects data from unauthorized access.
- Name-and-password authentication for Internet/intranet clients
  Name-and-password authentication, also known as basic password authentication, uses a basic challenge/response protocol to ask users for their names and passwords and then verifies the accuracy of the passwords by checking them against a secure hash of the password stored in Person documents in the Domino® Directory.
  - Authenticating web users against the Notes® ID passwords in the ID vault
    You can configure HCL Domino® to use the password in an ID vault to authenticate web users that access the server.
  - Setting up basic name-and-password authentication
    To enable basic name-and-password authentication, for both TCP and SSL, for all Internet protocols: Web (HTTP); IMAP; POP3; LDAP; SMTP Inbound; and IIOP, you must complete three separate procedures.
  - Session-based name-and-password authentication for Web clients
    To set up name-and-password authentication for Web clients who have access to a Domino® Web server, you can use one of two methods: basic name-and-password authentication or session-based name-and-password authentication. Session-based name-and-password authentication includes additional functionality that is not available with basic name-and-password authentication. A session is defined as the time during which a Web client is actively logged onto a server with a cookie. To specify settings that enable and control session authentication, you edit the Web Site document or the Server document, depending on your configuration.
  - Controlling the level of authentication for Internet clients
    You can select the level of restriction HCL Domino® uses when authenticating users in Domino Directories and LDAP directories, and the user has supplied a user name and password. This applies to all Internet protocols (HTTP, LDAP, IMAP, POP3).
    - Examples of name variations allowed for Internet client authentication
      The level of security partially depends on the number of name variations. Limiting the number of name variations users can employ during Internet authentication provides for greater security.
    - Authenticating Internet name-and-password clients in secondary Domino® and LDAP directories
      When an Internet client authenticates with a server, by default the server checks the primary HCL Domino® Directory to see if it can find a Person document with a name and password that match those entered by the Internet client. If your organization uses a secondary Domino Directory and/or an LDAP directory to verify Internet clients who use name-and-password authentication, you can set up Domino to check those additional directories. To do so, you set up the secondary Domino Directories and LDAP directories as trusted domains in the Directory Assistance database.
  - Managing Internet passwords
    To manage the Internet passwords that you assign to users who have Person documents in the Domino® Directory, use a security settings policy document. You can manage Internet password quality and length, as well as allow users to change their Internet passwords using a Web browser, and control expiration period and change intervals.
  - Anonymous Internet and intranet access
    When you set up anonymous access, Internet and intranet clients can access servers without identifying themselves. HCL Domino® does not record these clients' database activity -- for example, in the log file and in the User Activity dialog box.
  - Validation and authentication for Internet and intranet clients
    After you set up name-and-password access and create Person documents for Internet/intranet users, Domino® authenticates users either when they attempt to do something for which access is restricted, or Anonymous access is not allowed on the server.
- Multi-server session-based authentication (single sign-on)
  Multi-server session-based authentication, also known as single sign-on (SSO), allows Web users to log in once to a Domino® or WebSphere® server, and then access any other Domino or WebSphere servers in the same DNS domain that are enabled for single sign-on (SSO) without having to log in again.
- Using Security Assertion Markup Language (SAML) to configure federated-identity authentication
  Federated identity is a means of achieving single sign-on, providing user convenience and helping to reduce administrative cost. In Domino® and Notes®, federated identity for user authentication uses the Security Assertion Markup Language (SAML) standard from OASIS.
- Using a credential store to share credentials
  In this release, the on-premises Domino® server can use a credential store application (credstore.nsf). The credential store is a secure repository for document encryption keys and other tokens necessary for Notes® client users to grant access to applications that use the OAuth (open authorization) protocol. OAuth allows user credentials to be shared with compliant applications so that users avoid extra password prompts.

Authenticating Internet name-and-password clients in secondary Domino® and LDAP directories

When an Internet client authenticates with a server, by default the server checks the primary HCL Domino® Directory to see if it can find a Person document with a name and password that match those entered by the Internet client. If your organization uses a secondary Domino® Directory and/or an LDAP directory to verify Internet clients who use name-and-password authentication, you can set up Domino® to check those additional directories. To do so, you set up the secondary Domino® Directories and LDAP directories as trusted domains in the Directory Assistance database.

When you mark domains as trusted, Domino® first searches the primary Domino® Directory for the user name and password and then searches the trusted secondary Domino® Directories and LDAP directories. When you set up directory assistance, you specify the order in which Domino® searches the secondary directories.

The hierarchical name returned by the Domino® Directory or LDAP directory is checked against the trusted rule in the Directory Assistance database to verify that the organization and organizational units match the specified rule. For example, if the user name returned is Dave Lawson/Renovations, the Directory Assistance document must include the rule */Renovations.

Searching multiple directories is also available for authenticating users with SSL client authentication.

For clients in secondary LDAP directories, it is also possible to map the name in an LDAP directory to a Domino® name, using the field Attribute to be used as Notes distinguished name. In this case, the user may log in by specifying a valid LDAP name and password, and as a result of successful authentication is known within Domino® as the corresponding HCL Notes® distinguished name.