Home
Securing
This section describes security features, including execution control lists, IDs, and TLS.
Using Domino as an OIDC provider
The Domino HTTP task can act as an OIDC identity provider. This feature allows administrators to leverage their existing Domino HTTP authentication experience -- including passkeys, TOTP, custom domcfg login forms, and external identity providers -- to authenticate end users with applications, servers, and services that support OIDC.
Configuring Domino as an OIDC provider
To prepare a Domino server to be an OIDC identity provider, you must configure it in Domino's IdP Catalog application and in the Domino Directory's Internet Site document. You can then configure Domino as a clustered OIDC provider.
Dynamic custom claims and limiting access to OAuth clients
With Domino as OIDC provider, you can configure any number of custom claims that can use @functions to dynamically build claim values. Additionally, the Domino provider can perform access checking and deny unauthorized users the ability to even acquire an authorization grant for their application.

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.
- Using Domino as an OIDC provider
  The Domino HTTP task can act as an OIDC identity provider. This feature allows administrators to leverage their existing Domino HTTP authentication experience -- including passkeys, TOTP, custom domcfg login forms, and external identity providers -- to authenticate end users with applications, servers, and services that support OIDC.
  - Configuring Domino as an OIDC provider
    To prepare a Domino server to be an OIDC identity provider, you must configure it in Domino's IdP Catalog application and in the Domino Directory's Internet Site document. You can then configure Domino as a clustered OIDC provider.
    - Registering a new OAuth client
      Each application or website seeking to use a Domino OIDC provider for authentication must be registered as an OAuth client in idpcat.nsf.
    - Key Rotation
      Administrators can manually rotate (roll over) the keys that the Domino OIDC provider uses to sign and encrypt tokens.
    - Dynamic custom claims and limiting access to OAuth clients
      With Domino as OIDC provider, you can configure any number of custom claims that can use @functions to dynamically build claim values. Additionally, the Domino provider can perform access checking and deny unauthorized users the ability to even acquire an authorization grant for their application.
    - Troubleshooting the Domino OIDC provider
  - Domino OIDC provider HTTP endpoints
    The endpoints supported by the Domino OIDC provider are listed and described in the following sections.
  - Configuring Verse with OIDC login and Web federated login
    Configuring Verse with OIDC and Web federated login with OIDC allows Verse web users to authenticate and then perform secure mail operations such as signing and decrypting messages without being prompted for a Notes ID password.
  - Configuring Nomad server on Domino with OIDC login and Nomad federated login
    When the Nomad server on Domino is configured with OIDC login and Nomad federated login, Nomad users can authenticate through Domino as an OIDC provider and then set up Nomad clients without being prompted for their HCL Notes ID and password.
  - Configuring Verse Mobile with OIDC login
    Configuring HCL Verse Mobile and HCL Traveler with OIDC allows Verse Mobile users to authenticate through Domino as an OIDC provider prior to accessing the HCL Traveler services.
  - Configuring Notes with OIDC login
    Configuring HCL Notes with OIDC allows Notes client users to authenticate through Domino as an 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.

Dynamic custom claims and limiting access to OAuth clients

With Domino as OIDC provider, you can configure any number of custom claims that can use @functions to dynamically build claim values. Additionally, the Domino provider can perform access checking and deny unauthorized users the ability to even acquire an authorization grant for their application.

Dynamic custom claims

You configure dynamic custom claims in the Custom Claims field in the Registered OAuth Client document in idpcat.nsf.

Note:

Individual claims may not include the tilde '~' character.
The HTTPPassword may not be used in custom claims.
Excessively long custom claims may be truncated.

Limiting access to registered OAuth clients

Most Domino environments perform access controls at the resource being accessed through ACLs, reader and author fields, and so on. However, some third-party applications prefer to have their OIDC provider perform access checking and deny unauthorized users the ability to even acquire an authorization grant for their application.

To support this scenario, Domino has an "Allowed user group" field in the Advanced section of Registered OAuth Client documents in idpcat.nsf. By default, this field is blank and all authenticated users are allowed to acquire authorization grants for this client.

To limit access, add the name of a group containing the users who are allowed to use this client into the Allowed user group field on the primary Domino OIDC provider server, and save the document. The primary Domino server immediately processes this change and replicates it out to the secondary OIDC provider servers, with no restarts or manual replication required.