Home
Securing
This section describes security features, including execution control lists, IDs, and TLS.
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.
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.

Securing
This section describes security features, including execution control lists, IDs, and TLS.
- 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.
- TLS security
  Transport Layer Security (TLS) is a security protocol that provides communications privacy and authentication for Domino® server tasks that operate over TCP/IP.
- TLS and S/MIME for clients
  Clients can use a Domino® certificate authority (CA) application or a third-party CA to obtain certificates for secure TLS 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 users that access the server over HTTP, IMAP, POP3, and LDAP internet protocols.
  - Setting up basic name-and-password authentication
    To enable basic name-and-password authentication, for both TCP and TLS, 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).
  - 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.
  - Securing Internet passwords
    Internet passwords can be subject to attacks by malicious sources. However, there are measures you can take to make Internet passwords more secure.
  - 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.
    - Setting up Internet/intranet clients for anonymous access
      To set up Internet/intranet clients for anonymous access, you either set up the Internet Site or the server for anonymous access, and then set up database ACLs to include the entry Anonymous.
  - 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.
- Time-based one-time password (TOTP) authentication
  When users log on to a Domino Web server, you can require that they provide time-based one-time passwords in addition to their user names and passwords.
- 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 OpenID Connect (OIDC) to configure federated-identity authentication
  Federated identity is a means of achieving single sign-on, providing user convenience and helping to reduce administrative cost. One way that client applications can authenticate users is by using an OpenID Connect (OIDC) provider.
- Using a credential store to store credentials
  A Domino® server can use a credential store application as a secure artifact repository. Examples of secure artifacts include authentication credentials and security keys.
- History of supported key sizes in Notes and Domino
  Understand the RSA key sizes supported by Notes® and Domino® from past releases to the current release.

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.

With anonymous access, you never know who is accessing databases on the server. Therefore, you cannot use the client's identity -- that is, the client's name and password -- to control access to databases and design elements. Use anonymous access when you do not need to know who is accessing the database and/or when you do not need to control access based on client identity.

You can use anonymous access with TCP/IP and/or TLS on any server that runs LDAP, HTTP, SMTP, or IIOP. For each Internet protocol enabled on the server, you can specify the method of security. For example, you can enable TLS for HTTP connections, but require name-and-password authentication for LDAP connections that use TCP/IP.

In addition to using anonymous access, you can enable name-and-password authentication and TLS client authentication. Then users can use any authentication method to connect to the server. For example, if the user has an TLS client certificate, the user can access the server using TLS; whereas a user who does not have an TLS client certificate can access the server anonymously.