Home
HCL Sametime® Administration Guide 12
Securing
This section provides information on securing your HCL Sametime environments.
Enabling Single Sign-on
The HCL Sametime server installer enables required JSON Web Token (JWT) authentication. Additionally, the Sametime server supports Security Assertion Markup Language (SAML) and Lightweight Third Party Authentication (LTPA) Single Sign-on (SSO).
Setting up SSO using LTPA
You can implement SSO into your environment using Lightweight Third Party Authentication (LTPA) which requires LTPA keys.
Integrating Sametime with HCL Domino
This topic includes the procedure to enable LTPA when Sametime is integrated with the Domino server for use with web based mail, Verse and iNotes.

HCL Sametime® Administration Guide 12
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- New features in Sametime 12
  The current version of HCL Sametime and HCL Sametime Premium includes new features and enhancements.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime and HCL Sametime Premium.
- Configuring
  This section provides information on configuring the HCL Sametime server.
- Securing
  This section provides information on securing your HCL Sametime environments.
  - Encryption usage in Sametime
    HCL Sametime uses several types of encryption to protect data.
  - Securing connections
    The various interactions that occur on the Sametime server can be secured.
  - Enabling Single Sign-on
    The HCL Sametime server installer enables required JSON Web Token (JWT) authentication. Additionally, the Sametime server supports Security Assertion Markup Language (SAML) and Lightweight Third Party Authentication (LTPA) Single Sign-on (SSO).
    - Setting up SSO using LTPA
      You can implement SSO into your environment using Lightweight Third Party Authentication (LTPA) which requires LTPA keys.
      - Generating LTPA keys
        Lightweight Third Party Authentication (LTPA) uses keys to encrypt and decrypt data being passed.
      - Configuring LTPA in Docker or Podman
        This topic includes the steps to configure LTPA keys on Docker.
      - Configuring LTPA in Kubernetes
        This topic includes the steps to configure LTPA keys on Kubernetes.
      - Integrating with HCL Connections
        You can integrate Sametime to enable chat services in HCL Connections.
      - Integrating Sametime with HCL Domino
        This topic includes the procedure to enable LTPA when Sametime is integrated with the Domino server for use with web based mail, Verse and iNotes.
    - Setting up SSO using SAML
      You can implement SSO into your environment using Security Assertion Markup Language (SAML). The process is different for Kubernetes and Docker.
  - Enabling security in MongoDB
    To enable MongoDB securing, edit the mongod.conf file authorization: enabled setting.
  - Setting up TLS for the Mongo database
    You can update the MongoDB connection with the Sametime server to encrypt data flowing between the Sametime server and a TLS-enabled MongoDB. This step is optional but is recommended for multi-Kubernetes-cluster deployments.
  - Obtaining the cert.key and cert.crt files for Sametime
  - Replacing the TLS certificates for Web Chat and Meetings
    The Sametime server is pre-configured with a self-signed certificate. You can replace the self-signed certificate with a third-party certificate.
  - Applying Let's Encrypt certificates
    This topic describes how to replace the self-signed certificate with a third-party certificate.
- Administering
  This section provides information on administering on Sametime environments.
- Troubleshooting
  This section provides information on troubleshooting and supporting Sametime environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Migrating and Upgrading
  This section provides information on migrating data from an earlier release to Sametime 12.
- Notices

Integrating Sametime with HCL Domino

This topic includes the procedure to enable LTPA when Sametime is integrated with the Domino server for use with web based mail, Verse and iNotes.

Before you begin

Before you start you need an LTPA key which as an example can be generated by WebSphere Liberty. For more information on using WebSphere Liberty to generate LTPA keys, see Generating LTPA keys.

You also must configure the LTPA keys on the Sametime server.

About this task

To configure the Domino server, you must create a Web SSO configuration document and import the WebSphere LTPA keys. The following procedure describes the steps which are completed on the Domino mail server.

Procedure

Open the names.nsf and select the Web Configurations. Edit the Web SSO LtpaToken document.

Note: If a Web SSO LtpaToken document does not exit, it must be created from the Notes or Admin client Create menu. See Creating a Web SSO configuration document for the details.
Select Keys > Import WebSphere LTPA Keys.
Specify the path to the LTPA Keys file created following Generating LTPA keys and select OK.

Note: If prompted, select Format: LtpaToken and LtpaToken2 as the Use Token value.
Save and close the Web SSO LtpaToken document.
In the Domino mail server document under Internet Protocols - Domino Web Engine, select Multiple Servers (SSO) as the session authentication.
Start the Domino and Sametime servers to apply the changes. For more information, refer to Starting and stopping the Sametime server.