Home
Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
Securing
This section describes security features, including execution control lists, IDs, and SSL.
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.
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:

Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
- Translated documentation
  The HCL Domino 11.0.1 documentation is currently available in the following languages.
- What's new in Domino® 11?
  Learn about all of the new features for administrators in HCL Domino® 11.
- Overview
  Welcome to HCL Domino® Administrator Help.
- Domino trial
  A trial version of HCL Domino® 11.0.1 is available free of charge.
- Installing
  Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
- Planning
  Use this topic as an overview of planning task.
- Configuring
  Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
- Securing
  This section describes security features, including execution control lists, IDs, and SSL.
  - 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.
  - SSL security
    Secure Sockets Layer (SSL) is a security protocol that provides communications privacy and authentication for Domino® server tasks that operate over TCP/IP.
  - SSL and S/MIME for clients
    Clients can use a Domino® certificate authority (CA) application or a third-party CA to obtain certificates for secure SSL 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.
  - 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 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.
- Administering
  This documentation provides information about the administration tools for managing and monitoring servers and databases.
- Tuning
  Use this information to improve HCL Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, Server.Load commands, advanced database properties, cluster statistics, and the Server Health Monitor.
- Troubleshooting
  This section describes how to find and solve problems with HCL Domino® server and Administrator client.
- Notices

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:

Procedure

From the server you are removing from the cluster, use the following server console command to export the content of the credential store to a new database:
```
keymgmt export credstore <database> <local_server> 
```
where
- <database> is the name of a database to create to store the data.
- <local_server> is the Notes hierarchical name of the server.
For example:
```
keymgmt export credstore credstorecopy.nsf hubserver/renovations 
```
Rename the credstore.nsf file on the server. For example, rename it to credstore_orig.nsf
Change the Server document of the server to remove the server from the cluster. Then, restart the server.
Create a named encryption key for the new credential store to be created for the server:
```
 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 data from the database that you created in Step 1.
```
keymgmt import credstore <database>
```
where <database> is the name of the database. For example:
```
keymgmt import credstore credstorecopy.nsf
```