Home
Securing
This section describes security features, including execution control lists, IDs, and TLS.
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.
Moving a credential store in a clustered environment
When you add servers to or remove servers from clusters when credential stores are used, follow the steps that apply to your scenario to ensure that the credential store continues to function.
Moving a clustered server and credential store to a new cluster and credential store
Follow these steps to move a clustered server and credential store to a new cluster and credential store. These steps assume the server being moved is the first server in the new cluster.

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.
- 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.
  - Creating the credential store application on a single Domino® server
    Use keymgmt commands at the Domino® server console to set up the credential store for single-server use.
  - Creating the credential store application in a cluster
    Use keymgmt commands at the Domino® server console to set up the credential store application (credstore.nsf) for all servers in a cluster.
  - Moving a credential store in a clustered environment
    When you add servers to or remove servers from clusters when credential stores are used, follow the steps that apply to your scenario to ensure that the credential store continues to function.
    - Moving a single-server credential store to a new cluster
      Use the following steps to move a single server and its credential store to a new cluster and clustered credential store. These steps assume the server with the credential store you are moving is the first in the new cluster.
    - Moving a single-server credential store to an existing clustered credential store
      Follow these steps move a non-clustered server and credential store to an existing cluster and credential store.
    - Removing a server from a clustered credential store and setting it up with a single-server credential store
      Follow these steps to remove a server from a cluster and clustered credential store and set it up as a non-clustered server with a new credential store:
    - Moving a clustered server and credential store to a new cluster and credential store
      Follow these steps to move a clustered server and credential store to a new cluster and credential store. These steps assume the server being moved is the first server in the new cluster.
    - Moving a server and credential store from one cluster to another existing cluster
      Follow these steps to move a server and its credential store from one cluster to another existing cluster.
  - Moving the credential store from a decommissioned server to a new server
    Follow this procedure when you are decommissioning a server and want to move its credential store to another (target) server that isn't clustered.
- 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.

Moving a clustered server and credential store to a new cluster and credential store

Follow these steps to move a clustered server and credential store to a new cluster and credential store. These steps assume the server being moved is the first server in the new cluster.

Procedure

From a server in the current cluster, use the following server console command to export the current credential store data to a database on the server:
```
keymgmt export credstore <database> <local_server> 
```
where
- <database> is the name of a database to export the data to.
- <local_server> is the Notes hierarchical name of the local server.
For example:
```
keymgmt export credstore credstorecopy.nsf hubserver/renovations 
```
Rename the credstore.nsf file. For example, rename it credstore_orig.nsf
Change the Server document to specify the new cluster name and restart the server.
Create a named encryption key for the credential store to be created for the new cluster:
```
keymgmt create nek <nekname> 
```
For example:
```
keymgmt create nek credstorekey 
```
Use the new key to create a new credential store on the server:
```
keymgmt create credstore <nekname>
```
For example:
```
keymgmt create credstore credstorekey
```
Populate the new credential store with the contents of the database you created in Step 1.
```
keymgmt import credstore <database>
```
where <database> is the name of the database. For example:
```
keymgmt import credstore credstorecopy.nsf
```
Set up this credential store on the other servers in the cluster. For more information, see Step 2 in the procedure Creating the credential store application in a cluster.