Using Single Sign-On for Sametime and other Domino and WAS servers

Single Sign-On (SSO) is a feature that allows users not to be prompted to re-enter credentials as they move around from server to server in your environment. SSO is dependent upon a shared domain between servers, and this is something you need to consider when building your Sametime environment. For instance, a Community Server at http://im.mrkitebenefit.com will never be able to provide SSO to a Meeting Server at http://meet.lucyskydiamonds.com.

SSO works by having the first server you log into create an LTPAtoken and storing that in your browser. The token contains credentials that are then passed to subsequent servers you use. These servers trust the token-generating server and accept the LTPAtoken as verification that your credentials are valid so you will not be prompted for further credentials during your time logged into the server.

There are several aspects to SSO in your Sametime environment, and not all of them...