Enabling Single Sign On

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

About this task

It is required by the Sametime Proxy server. Typically no further configuration is required, but in some situations you may want to configure single sign on to work with other servers.

For example, if you have Sametime integration with Verse, you need to share the same single sign on with the Verse servers.

With SSO configured, users who log in once to any server in the configured DNS domain do not have to log in again when they access any other participating server. Enabling SSO between the servers also helps the Sametime® Connect Client as well. If the community server is in the single sign on domain, the component services can re-use the token from the Sametime® Connect Client to login to other services.

Fully Qualified Host names

When using single sign on, all servers must use the fully qualified host names (such as server.example.com) in order for the LTPA Tokens to be created correctly.