Home
Security
After setting up your initial IBM® Sametime® environment, you may want to make additional changes to safeguard information at your site, including limiting user access to certain features, using encryption, and modifying default security settings.
Setting up single sign-on for Sametime® clients
Configure servers for single sign-on (SSO) as a convenience to users running the IBM® Sametime® browser client. With SSO configured, users who log in once to any server in the DNS domain do not have to log in again when they access any other server running on IBM Domino® or WebSphere® Application 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.

Setting up single sign-on for Sametime clients

Configure servers for single sign-on (SSO) as a convenience to users running the IBM® Sametime® browser client. With SSO configured, users who log in once to any server in the DNS domain do not have to log in again when they access any other server running on IBM Domino® or WebSphere® Application 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.