Home
Securing
This section describes security features, including execution control lists, IDs, and TLS.
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.
Revoking a certificate
A CA administrator can easily revoke an Internet certificate -- for example, if the subject of the certificate leaves the organization, or if the key has been compromised. After a certificate is revoked, it can never again be trusted.

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.
  - Setting up a server-based Domino® certification authority
    You set up a server-based certification authority by setting up a certifier or certifiers, and then enabling them for the CA process.
  - Administering a Domino® CA
    There are a number of tasks associated with managing a HCL Domino® certifier. If you implement a certifier that uses the CA process, you can delegate HCL Notes® and Internet certificate request approval and denial to other administrators, each of whom acts as a registration authority. Many of the manual tasks associated with managing a CA in prior versions of Domino are automated when you use the CA process.
  - Migrating a certifier to the CA process
    To migrate an existing certifier to the CA process, you set up an Issued Certificate List (ICL) database and configure its certificate duration. In addition, for Internet certifiers, you configure CRL and key usage information for the certificate.
  - Adding a certifier to the CA process
    To manage the CA process, use Tellcommands at the server console.
  - Viewing certifiers running under the CA process
    You can view a list of all the certifiers running under the CA process.
  - Creating a certifier for a server-based CA
    You can create additional HCL Notes® and Internet certifiers for your organization and configure them to use the CA process.
  - Creating the Certificate Requests database
    Each Internet certifier you create requires a Certificate Requests database (CERTREQ.NSF) to manage the server keyring file and allow users to request client certificates from the browser or through email. This database stores active certificate and revocation requests that have been submitted to the Administration Process for processing. Using a browser-based interface, servers and clients request certificates and pick up issued certificates.
  - Setting up TLS on a server-based CA server
    Because server administrators and clients use browsers to access the CA server to request and pick up certificates, use TLS to protect the CA server. When you set up the CA server for TLS, you create the server key ring file and request a server certificate. Domino® automatically approves the server certificate and merges the CA certificate as a trusted root.
  - Signing server certificates using the Certificate Requests database
    A Domino® administrator can request a server certificate from a server-based CA in order to enable TLS on a Domino server. The request is entered and processed in the Certificate Request database, where administrators approve or deny the request.
  - Modifying a server-based CA
    After you migrate or create a certifier, you can modify it through the certifier ICL or through the certifier document in the Domino® Directory. How you open a certifier to modify it affects the number and type of changes you can make.
  - Viewing certificate requests
    Domino® CAAs and RAs can view information about server and client certificate requests waiting for approval, as well as approved and rejected requests.
  - Revoking a certificate
    A CA administrator can easily revoke an Internet certificate -- for example, if the subject of the certificate leaves the organization, or if the key has been compromised. After a certificate is revoked, it can never again be trusted.
  - Backing up and recovering a certifier
    Back up each certifier that you create, so that you can recover if there is a problem -- for example, if error messages are generated by the certifier when you issue a lo ca or tell ca refresh command.
  - Disabling a certifier
    To modify a Certifier document, you must have Editor access to the Domino® Directory. Full-access administrators and administrators have this access by default; however, be sure that all certificate authority (CA) administrators also have this access.
- 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.
- 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.

Revoking a certificate

A CA administrator can easily revoke an Internet certificate -- for example, if the subject of the certificate leaves the organization, or if the key has been compromised. After a certificate is revoked, it can never again be trusted.

About this task

If you revoke a certificate, especially if a key has been compromised, issue an immediate CRL so that any entity checking CRLs has the most updated revocation information.

Procedure

From the Domino® Administrator, click Files. Open the ICL directory.
From the list of ICL databases, open the ICL for the certifier that issued the certificate you need to revoke.
Open the Issued Certificates > By Subject Name view.
Open the Issued Certificate document for the certificate you want to revoke. The document name is the same as the subject name.
Click Revoke Certificate.
In the Revocation Reason dialog box, select the reason for revoking the certificate, and click OK. This sends a revocation request to the Administration Requests database.
Once you have made sure that the certifier has processed the revocation request and revoked the certificate, issue an immediate (non-regular) CRL.

Results

The next time the CA process refreshes, the Issued Certificate document will be updated to indicate that the certificate has been revoked. When you open the Issued Certificate document again, the Revocation Information section will indicate that the certificate has been revoked, the revocation date and time, the reason for the certificate's revocation, and date and time the certificate became invalid.