Home
Securing
This section describes security features, including execution control lists, IDs, and TLS.
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 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.
Configuring the primary domain for cross-domain TOTP authentication
Complete these steps to configure TOTP authentication for the primary domain.

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.
- 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.
  - 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.
    - Configuring the primary domain for cross-domain TOTP authentication
      Complete these steps to configure TOTP authentication for the primary domain.
    - Configuring the secondary domain for cross-domain TOTP authentication
      Complete these steps to configure TOTP authentication for the secondary 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 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.

Configuring the primary domain for cross-domain TOTP authentication

Complete these steps to configure TOTP authentication for the primary domain.

About this task

This procedure uses Domain1 for the primary domain name and Domain2 for the secondary domain name.

Procedure

Add the following notes.ini setting to all Web servers in Domain1 and to the ID vault server in Domain1:
ENABLE_IDV_CROSSDOMAIN_AUTHENTICATION=1
Ensure that the Domain1 Domino directory has a Notes cross-certificate at the /Org level for Domain2 that establishes trust.
Configure directory assistance to look up names in the Domain2 Domino directory:
1. Create a directory assistance database (if not created already) on a server in Domain1.
2. Add a Directory Assistance Document for Domain2. The following fields in the document are required.
  On the Basics tab:
  - Domain type Select Notes.
  - Domain name Specify the Domino domain of the secondary directory, for example Domain2.
  - Make this domain available to Select Notes Clients & Internet Authentication/Authorization
  - Enabled Select Yes.
  On the Naming Contexts (Rules) tab, select Enabled > Yes and Trusted for Credentials > Yes for at least one rule that applies to Domain2. You can use the default N.C. 1 rule.
  
  On the Domino tab, specify the replica of the Domain2 Domino directory on the Domain2 administration server.
  
  For additional information, see Creating a Directory Assistance document for a Domino Directory or extended directory catalog.
3. At the Domino server console, run the command sh xdir to verify the configuration. You should see output similar to the following output:
```
[11A4:0006-105C]  DomainName      DirectoryType         ClientProtocol Replica/LDAP Server
[11A4:0006-105C]    --------------- --------------------- -------------- -----------------------
[11A4:007C-105C]  1 Domain1        Primary-Notes         Notes & LDAP   names.nsf
[11A4:007C-105C]  2 Domain2        Secondary-Notes       Notes          server1/domain2!!names.nsf
```
Configure TOTP authentication for Domain1. For more information, see Configuring TOTP authentication.
Replicate the Domain1 Domino directory and Directory Assistance database to all participating Web servers in Domain1.