Home
Welcome to the HCL Sametime® 11.6 administration documentation
Securing
This section provides information on securing HCL Sametime 11.6 environments.
Enabling Single Sign-on
The HCL Sametime Community server uses the Domino server web server security features. By default the Sametime server installer configures single sign-on (SSO) for Domino.

Welcome to the HCL Sametime® 11.6 administration documentation
- 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.
- What's new in HCL Sametime
  This section describes what's new in HCL Sametime® 11.6 and Sametime® Meetings 11.6.
- Checklist to deploy Sametime
  This section provides information on reviewing the checklist to deploy the Sametime clients.
- Encryption usage in Sametime
  HCL® Sametime® uses several types of encryption to protect data.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime 11.6.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime 11.6.
- Configuring
  This section provides information on configuring the servers for HCL Sametime 11.6.
- Securing
  This section provides information on securing HCL Sametime 11.6 environments.
  - Installing GSKit on Microsoft Windows
    To install GSKit on Microsoft Windows, follow the steps:
  - Installing GSKit on Linux
    To install GSKit on Linux, follow the steps:
  - Securing connections
  - Enabling Single Sign-on
    The HCL Sametime Community server uses the Domino server web server security features. By default the Sametime server installer configures single sign-on (SSO) for Domino.
    - Enabling SSO on the Community Server
      The HCL® Sametime® Community Server uses authentication by token to authenticate connections that occur after a user has authenticated once using password authentication.
    - Altering the Domino® Web SSO configuration following the Sametime® server installation
      The HCL® Sametime® installation automatically enables and configures the Domino® SSO feature on the Domino® server. In some cases, it may be necessary to alter the default configuration of the Domino® SSO feature following the Sametime® server installation.
    - Enabling SSO for Connections and Sametime
      If you are enabling the Connections Profiles Photo URLs in your Sametime business card configuration, single sign on may be required in order for Sametime to access the URLs.
    - Enabling SSO between a SAML identity provider and the Sametime Community Server
  - Configuring the Sametime Proxy server for SAML authentication
    The Sametime Community server supports multiple authentication methods such as using a name and password, and Security Assertion Markup Language (SAML).
  - Enable Security in MongoDB
    To enable MongoDB securing, edit the mongod.conf file setting authorization: enabled.
  - Enabling TLS for the Mongo database
    You can update the MongoDB connection with the Sametime Community server to encrypt data flowing between the Sametime server and a TLS enabled MongoDB.
  - Updating the Sametime Meeting Server TLS Certificates
    This section provides information on updating the Sametime Meeting Server certificates.
  - Applying Let's Encrypt certificates on the Meeting server
- Administering
  This section provides information on administering HCL Sametime 11.6 environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Troubleshooting
  Troubleshooting and Support
- Migrating and Upgrading
  This section provides information on migrating and upgrading from an earlier Sametime release.
- Notices

Enabling Single Sign-on

The HCL Sametime Community server uses the Domino server web server security features. By default the Sametime server installer configures single sign-on (SSO) for Domino.

About this task

SSO is required by the Sametime Proxy server. Typically no further configuration is required, but in some situations you might need to configure SSO to work with other servers. For example, if you have Sametime Integration with Verse, you need to share the same SSO with the Verse servers.

With SSO configured, users who log in to any server within the configured DNS domain do not have to log in again when they access another participating server. Enabling SSO between the servers also helps the Sametime Connect Client. If the community server is within the SSO domain, the component services uses the token from the Sametime Connect Client to log in to other services.

Note: When using SSO all servers must use the fully qualified host names, such as server.example.com in order for the LTPA tokens to be created correctly.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.