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.
Passkey authentication
Learn how to enable passkey authentication on a Domino server or internet site for improved security.
Renaming and deleting users in the passkey database
Starting in 14.5, administrators can rename and delete users in passkey.nsf via AdminP. If you have existing passkey.nsf files or users created with a 14.0 server, you need to update to the new template to access this functionality.

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.
    - Optional passkey configurations
      Define additional configurations for passkey authentication.
    - Renaming and deleting users in the passkey database
      Starting in 14.5, administrators can rename and delete users in passkey.nsf via AdminP. If you have existing passkey.nsf files or users created with a 14.0 server, you need to update to the new template to access this functionality.
  - 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.
- 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.
- 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.

Renaming and deleting users in the passkey database

Starting in 14.5, administrators can rename and delete users in passkey.nsf via AdminP. If you have existing passkey.nsf files or users created with a 14.0 server, you need to update to the new template to access this functionality.

AdminP now handles requests for renaming and deleting users in the passkey database. To support this, the passkey.ntf template has been modified with new fields "NNUserDN" (non-abbreviated name) and "NNUserDisplayName" (user internet address). Therefore as a prerequisite to this functionality, the passkey database must be using the new template.

Updating the passkey database

If there are any existing passkey.nsf files using the 14.0 format, you must update their design. Additionally, any user entries that were previously created in the passkey database need to be updated with the new passkey form. To accomplish this, from the passkey database click Actions > Update document design.

This action updates all existing users to the new design. You only need to run this once, as any user created with a 14.0.1 server will have the new format by default.

How it works

When you rename a user through AdminCentral, the "Rename in Reader/Author fields" AdminP request initiates. When it finishes processing, the user's distinguished name and internet address are updated in the passkey database. This AdminP request runs on the delayed request setting in the server document, which defaults to Sunday at 12 am.

Similarly, deleting a user initiates the "Delete in Reader/Author fields" AdminP request, also a delayed request. When it finishes processing, the user's entry is deleted in the passkey database.