Integrating with HCL Verse
This topic includes the steps required to configure Sametime integration with HCL Verse.
Before you begin
For Single Sign-On (SSO) to function correctly with Verse, the user identity must be consistent in Sametime and HCL Verse. Sametime uses the email address to identify the user; therefore, the LDAP directory used by Sametime must return the same email address used in Verse.
LTPA SSO requires both servers to share the same DNS suffix (for example, example.com), and each hostname participating in the SSO must have a fully qualified domain name consisting of at least three parts. For instance, verse.example.com and sametime.example.com.
LTPA SSO does not support IP addresses or shortnames.
Procedure
Complete the following steps on an HCL Verse server.
-
Complete the steps from the Domino documentation. Refer to Configuring integration with HCL Sametime.
-
Complete the steps in the Integrating Sametime with Domino topic. Refer to Integrating Sametime with HCL Domino.
Complete the following steps on an HCL Sametime server.
-
Complete the following steps to enable web client integration.
a. Instructions for Docker or Podmon. Refer to Enabling web client integration on Docker and Podman
b. Instructions for Kubernetes. Refer to Enabling web client integration on Kubernetes
-
Complete the following to enable content security headers
a. Instructions for Docker or Podmon. Refer to Enabling content security headers on Docker and Podman
b. Instructions for Kubernetes. Refer to Enabling content security headers on Kubernetes
-
Configure Cross Origin Resource Sharing (CORS). Refer to Configuring CORS
-
Apply these changes in the environment.
a. Instructions for Docker or Podmon. Refer to Applying configuration changes in Docker or Podman
b. Instructions for Kubernetes. Refer to Applying configuration changes in Kubernetes or Openshift
Related: