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.
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.
Configuring HTTP Bearer authentication using an OIDC provider
Client applications such as native apps, mobile apps, Progressive Web Apps (PWAs), and Single Page Apps (SPAs) can use HTTP bearer authentication with signed JWT access tokens acquired from an OIDC provider to authenticate to Domino servers.
Customizing HTTP Bearer authentication
In Domino 14.0, all of the configuration notes.ini variables from 12.0.2 have been removed and replaced with settings in idpcat.nsf.

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.
  - 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.
    - Preparing for OIDC authentication
      The tasks in this section are prerequisites to using both HTTP Bearer authentication using an OIDC provider and configuring SSO for web clients using an OIDC provider.
    - Configuring HTTP Bearer authentication using an OIDC provider
      Client applications such as native apps, mobile apps, Progressive Web Apps (PWAs), and Single Page Apps (SPAs) can use HTTP bearer authentication with signed JWT access tokens acquired from an OIDC provider to authenticate to Domino servers.
      - Enabling HTTP Bearer authentication
        Enable authentication using Bearer tokens in the Server Document or the Internet Site Document in the same manner as Basic and TLS Client Certificate authentication.
      - Customizing HTTP Bearer authentication
        In Domino 14.0, all of the configuration notes.ini variables from 12.0.2 have been removed and replaced with settings in idpcat.nsf.
    - Configuring Web Login with OIDC for web users
      A Single Sign-On (SSO) option for browser clients is available using the Open ID Connect (OIDC) authorization code flow with PKCE.
- 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.

Customizing HTTP Bearer authentication

In Domino 14.0, all of the configuration notes.ini variables from 12.0.2 have been removed and replaced with settings in idpcat.nsf.

Bearer authentication settings in idpcat.nsf

Microsoft's Active Directory Federation Services (ADFS) and Azure AD providers do not adhere closely to the OIDC specification. To configure Domino to be aware of and to tolerate this behavior, set the "Enable Microsoft work-arounds" checkbox in the Options field of idpcat.nsf.
JWTs must contain a form of the end user's name or email address that Domino can find uniquely in the Domino directory. If the "Custom email claim name" field is set in idpcat.nsf, Domino will check first for a claim with that specified name. If that custom claim name is not configured or the claim is not found, Domino will check for the standard "email" claim next, and will finally check for the "upn" claim.
By default, one of the JWT's "aud" (audience) claims must match the Domino Internet Site's host name, such as https://ultraviolet.example.com. If your OIDC Provider (OP) cannot be configured to send the correct resource name, the "Alternate audiences" field in idpcat.nsf can be populated with your OP's preferred value. For example, Azure AD may only send aud Claims in the form of a random guid that they generated themselves.
If you want to allow only JWTs that were issued to a limited set of trusted applications (by client_id), you can configure the "Allowed client IDs" field in idpcat.nsf with those permitted client_ids. If a nonzero set of allowed client_ids was configured, one of those client_ids must be found in the "azp" claim for the JWT to be valid.

Tracing configuration via notes.ini settings

The current list of notes.ini settings for 14.0 only includes tracing:

DEBUG_HTTP_BEARER_AUTH=(0,1,2,3,4)

DEBUG_OIDC_CONFIG=(0,1,2,3)

DEBUG_OIDC_CACHE=(01,2,3,4,5,6)

DEBUG_JWS=(0,1,2,3,4)

DEBUG_OIDC_CURL_APIS=(0,1,2,3,4)

DEBUG_OIDC_JSON_PARSER=(0,1,2,3)