Home
IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
Securing
This section describes IBM® Domino® security features, including execution control lists, IDs, and SSL.
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.
Configuring basic SAML authentication for Web servers
Complete the following tasks to enable basic SAML authentication for Web servers.
Enabling SAML authentication in Domino
Use this procedure to enable SAML authentication in the Domino directory. Enable SAML in an Internet Site document or in individual Server documents.

IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
- What's new in IBM® Domino® 10?
  Learn about all of the new features for administrators in IBM® Domino® 10.
- Overview
  Welcome to IBM® Domino® Administrator Help.
- Installing
  Use this documentation to install the IBM® Domino® server and subsequently deploy the IBM Notes® client.
- Planning
  Use this topic as an overview of planning task.
- Configuring
  Use this information to configure an IBM® Domino® network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters. Also use this information to set up IBM iNotes® on a server using Domino Off-Line Services (DOLS).
- Securing
  This section describes IBM® Domino® 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.
    - Preparing for SAML authentication
      Complete the steps in this section before you configure SAML authentication in Domino
    - Configuring basic SAML authentication for Web servers
      Complete the following tasks to enable basic SAML authentication for Web servers.
      - Creating a Web server IdP configuration document
        Create an IdP configuration document for Web servers that will participate in SAML authentication.
      - Exporting the Domino web configuration to an .xml file
        Complete this task to export the configuration information in a Web server IdP configuration document to an .xml file, ServiceProvider.xml. Then, you can import it into the Relying party trust (ADFS) or partnership (TFIM) to fill in the Domino information automatically.
      - Setting up a Relying Party Trust for Web servers
        Set up a Relying Part Trust in Active Directory Federated Services (ADFS) for Domino web servers that participate in SAML authentication. These procedures describe steps for ADFS 3.0 and ADFS 4.0.
      - Enabling SAML authentication in Domino
        Use this procedure to enable SAML authentication in the Domino directory. Enable SAML in an Internet Site document or in individual Server documents.
      - Testing basic SAML authentication
        Test basic SAML authentication to ensure that SAML authentication works for accessing web applications.
    - Configuring ID vault servers for 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.
    - 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 share credentials
    In this release, the on-premises Domino® server can use a credential store application (credstore.nsf). The credential store is a secure repository for document encryption keys and other tokens necessary for Notes® client users to grant access to applications that use the OAuth (open authorization) protocol. OAuth allows user credentials to be shared with compliant applications so that users avoid extra password prompts.
- Administering
  This documentation provides information about the administration tools for managing and monitoring IBM Domino® servers and databases.
- Tuning
  Use this information to improve IBM® 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 IBM® Domino® server and Administrator client.
- Glossary

Enabling SAML authentication in Domino

Use this procedure to enable SAML authentication in the Domino directory. Enable SAML in an Internet Site document or in individual Server documents.

About this task

If you later change the authentication type in an Internet Site document to remove SAML, your change has no effect to disable SAML unless the IdP Configuration documents are either disabled or deleted.

Procedure

Do one of the following from the Domino Administrator client:
- If you use an Internet Site document, select Configuration > Web > Internet Sites. Then, open the Internet Site document in which to enable SAML authentication.
- If you do not use an Internet Site document, select Configuration > Web > Web Server Configurations. Then, open the Server document in which to enable SAML authentication.
Click the Domino Web Engine tab.
In the Session authentication field, select SAML.
(Best practice) For Web SSO Configuration, select the existing configuration document you want to use. If the value for this field is specified, the SAML service provider uses the LTPA configuration specified in the SSO configuration document as the session cookie.
Leave the default of No specified for Force login on SSL.
The SAML single server session expiration field specifies the number of minutes the SAML session will be valid on the participating server. Leave the default of 120 minutes specified unless your organization's security requires a shorter or longer time than 2 hours for client users to have access using SAML. When the session expires, the SAML user must re-authenticate with the SAML IdP.
Leave Yes specified for When overriding session authentication, generate session cookie.
Open the IdP configuration document you created in the IdP Catalog and change State to Enabled.