Microsoft Office Communicator Web Access (2007) Authentication Guide

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Communicator Web Access (2007 release) has improvements to the 2005 release of Communicator Web Access that add support for custom authentication, including support for single sign-on (SSO) and two factor authentication. Many of these code improvements are changes made to the underlying Communicator Web Access authentication mechanisms, accessible from the Unified Communications AJAX application programming interface (API).

User authentication has value in applications such as those that implement the Unified Communications API. The primary purpose of such an application is to allow remote users to participate in IM conversations. The Communicator Web Access server does not provide support for video in an IM session. For this reason, a remote user can not see and validate the identity of the person she is conversing with. It is important that a user participating in an IM session can trust that other participants have been authenticated by the Communicator Web Access server. Without authentication, a user might not know that she is interacting with the actual person represented by the published identity of the remote user.

This guide gives an overview of the various authentication and integration methods that can be used for deploying Communicator Web Access and when developing custom solutions.

In This Section




Presents an overview of two user authentication methods available to Unified Communications applications


This section discusses using the SDK to test your authentication solution

See Also


Unified Communications AJAX SDK