Testing Authentication Implementations
This section discusses using the SDK to test your authentication solution.
The SDK includes Web-based samples and samples based on the Microsoft Win32® application programming interface. To install the SDK, double-click the SetupSE.exe or SetupEE.exe file on the Office Communications Server 2007 installation media, click Deploy Other Server Roles, click Deploy Communicator Web Access, click the Download the Communicator Web Access SDK link, and then follow the instructions. The SDK default installation folder is %Program Files%/Microsoft Office Communications Server 2007/ Unified Communications AJAX SDK/. Three subfolders are installed, /Docs, /Samples, and /Schemas.
Any integrated development environment can be used to develop these applications. However, the SDK code samples require the Microsoft Visual Studio® 2005 integrated development environment.
The Unified Communications AJAX SDK includes a Unified Communications AJAX API sample.
Figure 1: The UCAjaxManagedSample SDK Sample
The Communicator Web Access (2007 release) Service is accessible via the Unified Communications AJAX API that publicly exposes a subset of methods and events. ISVs can develop applications by following the AJAX programming patterns. Various programming languages, platforms, and operating systems are supported. The Unified Communications AJAX API uses XML as the data format and supports modularized access of the following functionality:
A Unified Communications AJAX API Client signs in to Communicator Web Access by using Forms-based authentication.
A Unified Communications AJAX API Client signs in to Communicator Web Access using Integrated Windows authentication.
A Unified Communications AJAX API Client signs in to Communicator Web Access by using custom authentication (such as single sign-on and two factor authentication).
The Unified Communications AJAX API Client posts methods to Communicator Web Access.
The Unified Communications AJAX API Client receives events from Communicator Web Access.
Applications developed by using the AJAX programming model can enable users to do the following:
Sign in and out of Communicator Web Access using a supported client.
Manage and share presence information.
Manage contacts and groups.
Send and receive instant messages.
Search for users within an enterprise.
Redirect voice call.
These clients can be a browser-based Web application (for example, an ASP.NET v2.0 application) or a standalone network application (for example, a .NET-connected executable, a Win32-based standalone application, or a UNIX-based C/C++ application). Because the Unified Communications AJAX API is based on the flexible AJAX programming model, the client applications are not limited to running on Microsoft Windows operating systems and can readily be deployed to desktop, laptop, or other devices.
Creating an application that accesses the Unified Communications AJAX API involves implementing the following:
The ISV application must sign in to a Communicator Web Access Server using either Forms-based authentication, Integrated Windows authentication, or custom authentication.
The client must then contact the Communicator Web Access Server to initiate the session.
The client must post one or more AJAX methods to the Communicator Web Access Server to do the following:
Manage contacts or groups.
Set or query presence.
Configure access control.
Start an instant messaging session, send and receive text messages, or close the IM session.
The client must be able to receive AJAX events from the server to do the following:
Execute a method and return the result.
Respond to a change in the server load and return a new query timeout value.
Sign a contact in or out and return the affected contact information.
Invite a user to join an IM conversation, accept the IM invitation, or send and receive instant messages during a conversation.
The client must sign out of the service and terminate the session.
As a result of a change to the Office Communications Server 2007 schema, Communicator Web Access (2007 release) no longer must retrieve a user’s SIP URI during sign-in. This means that the user name and password are the only pieces of information that need to be provided during sign-on.
Because Communicator Web Access (2007 release) does not require users to enter their SIP address when signing in, Communicator Web Access can use the same set of credentials that are used to sign into other applications. This ability to reuse credentials allows Communicator Web Access to be used in conjunction with automatic sign-in solutions.
The user must be enabled for Microsoft Office Communications Server 2007 and for remote access in the Active Directory® Users and Computers snap-in for internal and remote access, respectively.