Home
Securing
This section describes security features, including execution control lists, IDs, and TLS.
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.
Nomad federated login
Nomad federated login avoids users being prompted for their HCL Notes ID passwords when they set up the HCL Nomad for web browsers client. Instead, they are prompted only for credentials from a SAML identity provider (IdP) that is accessed through the Nomad server (SafeLinx); the users don't need to enter their Notes ID passwords.
Prerequisites for Nomad federated login
Before you configure Nomad federated login, make sure you've completed these prerequisite steps.

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.
  - Preparing for SAML authentication
    Complete the steps in this section before you configure SAML authentication in Domino
  - Configuring basic SAML authentication for Web servers
    Basic SAML authentication for Web servers allows browser clients to access the Domino Web server by authenticating with SAML. Complete the following tasks to enable basic SAML authentication for Web servers.
  - Configuring ID vault servers for Notes or Web federated SAML login
    Complete the steps in this section if you want to use Web federated login or Notes federated login. After enabled, iNotes users and Notes client users, respectively, access the Notes ID file in the ID vault without being prompted for the password. If your IdP is ADFS, you can also configure Integrated Windows Authentication (IWA) so that iNotes users or Notes clients users aren't prompted for the IdP name and password.
  - Enabling Web federated login
    Enable Web federated login to allow iNotes users to perform secure operations such as signing and decrypting messages without being prompted for a Notes ID password.
  - Enabling Notes federated login
    Enable Notes federated login to allow Notes clients users to start Notes and perform secure operations without being prompted for a Notes ID password.
  - Nomad federated login
    Nomad federated login avoids users being prompted for their HCL Notes ID passwords when they set up the HCL Nomad for web browsers client. Instead, they are prompted only for credentials from a SAML identity provider (IdP) that is accessed through the Nomad server (SafeLinx); the users don't need to enter their Notes ID passwords.
    - Prerequisites for Nomad federated login
      Before you configure Nomad federated login, make sure you've completed these prerequisite steps.
    - Nomad federated login configuration components
      Configuring Nomad federated login involves the following components. Note that there are additional prerequisite components beyond these as described in nomadfl_prerequisites.html.
    - Creating an IdP Configuration document for Nomad federated login
      Create an IdP Configuration document for Nomad federated login in idpcat.nsf.
    - Setting up a Relying Party Trust for the ID vault server used by Nomad federated login
      After you create the IdP configuration document for Nomad federated login and export the ServiceProvider.xml file, set up a relying party trust for your IdP to import the ServiceProvider.xml file into your IdP.
    - Enabling Nomad federated login
      After setting up a Relying Party Trust, enable Nomad federated login in the Security Settings policy used for the ID vault and in the ID vault document.
    - Exporting Notes certificates to a deploy.nsf file
      After you enable Nomad federated login, export the Notes organization certifier used by Nomad for web users to a deploy.nsf database.
    - Troubleshooting Nomad federated Login
      If Nomad federated login is working, a user who has not set up Nomad for web browsers can connect to the Nomad server without being prompted for a Notes ID during setup. If you encounter a problem with Nomad federated login, the following sections describe common issues and workarounds.
  - Enabling IWA (ADFS only)
    When Integrated Windows Authentication (IWA) is used, users on Windows clients are not prompted for the ADFS login name and password when they access servers on the corporate intranet. IWA is available for basic SAML authentication, Notes federated login, and Web federated login.
  - Generating a certificate to encrypt SAML assertions
    Your organization may require SAML assertions to be encrypted if assertions include attributes that contain sensitive personal data, for example, social security numbers. Domino® encrypts entire SAML assertions; partial encryption of specific attributes is not available.
  - Cautioning client users about SAML and logout
    Domino® and Notes® do not support a single logout feature, so if you configure SAML in your organization, make sure that your users employ safety methods at their desktops to prevent physical access to Notes and Domino resources.
- 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.

Prerequisites for Nomad federated login

Before you configure Nomad federated login, make sure you've completed these prerequisite steps.

Upgrade the Domino ID vault servers that are used by Nomad for web browser users to V12.0.1. In addition, upgrade the design of vault.nsf, names.nsf, and idpcat.nsf using the vault.ntf, pubnames.ntf, and idpcat.ntf templates provided with V12.0.1. These templates include functionality and fields used for Nomad federated login.
Set up a SAML identity provider (IdP) that is compatible with AuthnRequest SAML 2.0. Active Directory Federation Services (ADFS) is one example of an IdP but there are several others.
Set up the Nomad server. For more information, see Configuring the Nomad server in the Nomad administration documentation.
Configure SAML authentication on the Nomad server. When this step is complete, Nomad for web browser users authenticate through your IdP rather than the Nomad (SafeLinx) server. For information, see the topic Configuring SAML authentication in the SafeLinx documentation. Note that during initial Nomad for web browser client setup, users still need to log in to Domino with their Notes ID passwords until you configure Nomad federated login.
If you have not configured Domino for SAML authentication for another purpose, complete the following general steps required for Domino SAML authentication:
- Creating and replicating the IdP Catalog.
- Exporting a metadata .xml file from your IdP
- (ADFS only) Verify that the content of the following two fields match for each user:
  - The Internet address field in the Domino directory Person document.
  - The E-mail field in the user ADFS properties box.
- (ADFS only) if user addresses in the Active Directory mail attribute are not identical to addresses in the Internet Address field in Domino directory Person documents, see Configuring directory name mapping (ADFS only).
- Ensure that the SAML IdP computer and the Domino ID vault servers have their clocks synchronized so that these computers share the same notion of current time. For more information, see the section Clock Synchronization in the topic Completing Domino prerequisites for SAML. (Ignore other information in that topic; it doesn't apply to Nomad federated login.)