Figure 21–8 illustrates authentication process used by the Instant Messaging software in collaboration with Portal Server and Access Manager components in a single sign-on environment. As with Figure 21–2, this figure focuses on the flow of authentication requests. An explanation of the steps in this process follows the figure.
The authentication process of the Instant Messaging server in this deployment within a single sign-on environment works as follows:
The end user logs in to the Portal Server by entering the URL in a web browser.
The Access Manager software authenticates the end user and returns a session token and the Portal Server downloads the Desktop for the end user. The Portal Server Desktop is displayed in the end user’s browser. See Step 6 for an explanation of the session token.
The end user clicks the Instant Messenger URL link from the Instant Messaging channel on the Desktop.
Java Web Start or the Java plugin downloads the necessary Instant Messenger resource files and starts the Instant Messenger.
Instant Messenger requests authentication to the Instant Messaging server using the session token.
The session token is what enables single sign-on to work. This token is provided as an applet parameter and is used throughout the authentication process. End users are not asked for their credentials again as long as the session token is present.
The Instant Messaging server asks Access Manager to validate the session token. If the session is valid, Instant Messenger displays the end user’s contact list and the end user can then use Instant Messenger services: chat, alerts, polls, and so forth.
The Instant Messaging server must query LDAP directly to get or set end-user information, such as contact lists or subscriptions.