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.
Configuring single sign-on with Microsoft™ Windows™ Active Directory
The Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) replaces Microsoft™ Windows™ Single Sign-On, which is no longer supported by IBM® Sametime®. If the IBM Sametime Community Server uses a Microsoft Windows Active Directory, you must integrate all server components to allow Sametime users to log in and authenticate only once at their desktop and thereafter automatically authenticate with the Sametime server.

Configuring single sign-on with Microsoft Windows Active Directory

The Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) replaces Microsoft™ Windows™ Single Sign-On, which is no longer supported by IBM® Sametime®. If the IBM Sametime Community Server uses a Microsoft Windows Active Directory, you must integrate all server components to allow Sametime users to log in and authenticate only once at their desktop and thereafter automatically authenticate with the Sametime server.

About this task

For more information,

see the section on implementing single sign-on in the WebSphere® Application Server product documentation: Creating a single sign-on for HTTP requests using SPNEGO Web authentication
see this topic in IBM developerWorks®: Integrating SPNEGO with IBM Sametime components on a federated deployment