Home
Securing
This section describes security features, including execution control lists, IDs, and TLS.
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.
Setting up the Web SSO Configuration document for more than one Domino® domain
You can enable servers in your current Domino® domain for single-sign on (SSO) with servers in another Domino domain, by setting up both domains to use the same key information.

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.
  - Creating a Web SSO configuration document
    The Web SSO configuration document is a domain-wide configuration document stored in the HCL Domino® Directory. This document, which should be replicated to all Domino servers participating in the single sign-on domain, is encrypted for participating servers and administrators, and contains a shared secret key used by servers for verifying user credentials.
  - Enabling single sign-on and basic authentication
    This procedure ensures that a server can participate in single sign-on (SSO). An SSO-enabled server creates single sign-on cookies for users, allowing them to log in to the server and then be able to access other participating servers without having to log in again.
  - Setting up the Web SSO Configuration document for more than one Domino® domain
    You can enable servers in your current Domino® domain for single-sign on (SSO) with servers in another Domino domain, by setting up both domains to use the same key information.
  - Configuring user name mapping in the SSO LTPA token
    The LTPA token that is created to authenticate users for single sign-on includes the name of the user who has been authenticated. When HCL Domino® creates an LTPA token, it places the Domino distinguished name in the token by default. If a IBM® WebSphere® Application Server server obtains the token from a user trying to access the server, the Websphere server must be able to recognize this name format. If it does not, the token is ignored, single sign-on fails, and the user is prompted to log in again.
  - Caching Internet password changes for SSO
    When Web users change their Internet passwords, the HCL Domino® HTTP server remembers the new Internet password in its cache. Caching is required because it can take some time for the password change to take effect, as the change must be processed by the Domino administration server and replicated throughout the Domino environment.
  - Setting up Windows™ single sign-on for Web clients
    You can set up a Domino® Web server to honor Microsoft™ Windows™ users' Active Directory logon credentials. Web users who are logged on to the Active Directory domain can open applications on the server from a browser without being prompted for a password.
- 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.

Setting up the Web SSO Configuration document for more than one Domino® domain

You can enable servers in your current Domino® domain for single-sign on (SSO) with servers in another Domino® domain, by setting up both domains to use the same key information.

Before you begin

Two conditions must exist:

You must be a registered Notes® user and your server must be a registered server. This gives you and the server the access rights needed to decrypt the Web SSO Configuration document in your current domain, and to create documents in the Domino® Directory for the new domain. It may be necessary to have administrative IDs cross-certified for operating in the two domains.
The server document and the administrator's person document must exist in the domain for which you will be creating the Web SSO Configuration, as the public keys that are used for encryption are stored in each registered person and server document.
Participating SSO servers must still reside in the same DNS domain -- for example, renovations.com.

Procedure

Copy the Web SSO Configuration document from the Domino® Directory in which it was created, and paste it into the Domino® Directory in the new domain.
Open the Web SSO Configuration document for the new domain and edit the Participating Domino Servers field to include only those servers with server documents in the new domain that will be enabled for single sign-on.
The client must be able to find server documents for the participating single sign-on servers. Make sure that the home server specified in your client's location document is pointing to a server in the same domain as those servers participating in single sign-on, so that lookups will be able to find the public keys of the servers. If the home server cannot find participating servers, then the SSO document cannot be encrypted and SSO will fail.
Save the document. It is encrypted for the participating servers in the new domain, and should enable those servers in the new domain to participate in single sign-on with servers in the current domain.