Home
Securing
This section describes security features, including execution control lists, IDs, and TLS.
Web-based authentication
Define and set up authentication methods for web users, for example through basic password authentication, passkeys, time-based one-time password, or single sign-on.
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.
Configuring TOTP authentication
To configure time-based one-time password authentication (TOTP), complete the following steps.
5. Configuring the TOTP login form
Create a Domino Web Server Configuration database that uses the custom login form $$LoginUserFormMFA.

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.
- Web-based authentication
  Define and set up authentication methods for web users, for example through basic password authentication, passkeys, time-based one-time password, or single sign-on.
  - 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.
  - Passkey authentication
    Learn how to enable passkey authentication on a Domino server or internet site for improved security.
  - 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.
    - Prerequisites for TOTP authentication
      An overview of the prerequisites for TOTP authentication.
    - Configuring TOTP authentication
      To configure time-based one-time password authentication (TOTP), complete the following steps.
      - 1. Issuing a Multi-Factor Authentication Certificate
        To allow the use of time-based one-time password (TOTP) authentication, use the mfamgt server command to issue a Multi-Factor Authentication Certificate for the the organization unit (OU) or organization (O) of those users that will be using TOTP.
      - 2. Enabling TOTP authentication in the Configuration Settings document
        Enable TOTP on Domino® servers through a Configuration Settings document.
      - 3. Enabling TOTP authentication on servers
        After enabling TOTP authentication in a Configuration Settings document, also enable it on servers through a Server document, Internet Site document, or Virtual Server document.
      - 4. Enabling secure mail operations for TOTP
        You can optionally configure support for secure mail operations (decryption, encryption, signing) for web users with Notes IDs, such as iNotes users.
      - 5. Configuring the TOTP login form
        Create a Domino Web Server Configuration database that uses the custom login form $$LoginUserFormMFA.
      - 6. Restarting the vault server to enable TOTP
        After completing all configuration steps, restart the vault server.
    - Configuring cross-domain TOTP authentication
      You can enable TOTP authentication for users in a secondary Domino domain. When configuration is complete, users registered in the secondary domain can set up and use TOTP authentication that is configured in the primary Domino domain.
    - Docker considerations for TOTP authentication
      Requirements and recommendations for enabling TOTP on a Domino server on Docker are as follows.
    - Checking TOTP configuration
      Administrators can check Person, Server, Server Configuration, and Internet Site documents for proper configuration using the TOTP configuration checker.
    - How users set up TOTP
      After you enable time-based one-time password (TOTP) authentication on a Domino server, the next time web users log on to the server, they follow these steps to set up TOTP.
    - Resetting users' TOTP configurations
      If users are unable to provide valid TOTP tokens to log on to a TOTP-enabled server, you can reset their TOTP configurations so that they can set up TOTP again.
    - notes.ini settings for TOTP
      The following server notes.ini settings are available to customize the TOTP configuration.
  - 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 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.

5. Configuring the TOTP login form

Create a Domino Web Server Configuration database that uses the custom login form $$LoginUserFormMFA.

About this task

Follow this procedure to configure a login form for a generic Domino web server hosting web applications. To configure a TOTP login form for HCL iNotes, you instead use an application created from the IWAREDIR.NTF template. For information on configuring a TOTP login form for iNotes, see the section Setting up iNotes redirect in the topic Using iNotes Redirect to access mail in iNotes.

Procedure

Create the Domino Web Server Configuration database (DOMCFG.NSF):
1. From the Domino® Administrator choose File > Application > New.
2. Enter the name of the Web server in the Server field.
3. Select Show Advanced Templates.
4. Select the Domino® Web Server Configuration template (DOMCFG5.NTF).
5. Enter a title for the database.
6. In the File name field, enter DOMCFG.NSF.
  
  Important: The name of the database must be DOMCFG.NSF.
7. Click OK.
Specify $$LoginUserFormMFA as the log-in form:
1. Open the Domino® Configuration database (DOMCFG.NSF) and open the Sign In Form Mappings view.
2. Click Add Mapping.
3. Under Site Information, choose one:
  - All Web Sites/Entire Server -- to use the custom log-in form for all Web Sites on the server, or for the entire Web server.
  - Specific Web Sites/Virtual Servers -- to map the custom log-in form to specific Web Site documents or Virtual Servers. If you choose this option, a new field appears, in which you specify the IP addresses of the Web Site documents or Virtual Servers
4. Under Form Mapping, for Target Database specify DOMCFG.NSF and for Target Form, specify $$LoginUserFormMFA.
5. Save and close the document.
Make sure that the -Default- entry in the ACL of DOMCFG.NSF has Reader access with Read public documents enabled: