Terminology in Unified Communications AJAX SDK
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.
A single active session with Microsoft Office Communications 2007 Server, which can be initiated by any Communicator-compatible client that includes Office Communicator 2007, Communicator Web Access Web client, or Unified Communications AJAX API client. A single user may have multiple endpoints active simultaneously.
This is a form of authentication where the user credentials (domain, username, and password) are submitted by the client in plain text within the logon request. To provide compatibility with a variety of different Web browsers and support all scenarios, the Unified Communications API in combination with Communicator Web Access Server supports this form of authentication. When setting up an external Communicator Web Access Server for access from across an enterprise firewall, it is the only form of authentication supported. Computers that are not running a version of Microsoft Internet Explorer Internet browser can only use Form-based authentication.
Also known as an HTTP request and response transaction. A transaction begins when a client submits a request against a specified resource or service on the server. The transaction ends when the server responds with the requested resource or a form of acknowledgment of the request. The transaction can be synchronous or asynchronous. In a synchronous transaction, the client blocks until the server responds. In an asynchronous transaction, the client does not wait for the server to respond. Instead, the client registers a callback function with the server to receive the response from the server. With the Communicator Web Access Server, four types of HTTP requests are used for signing in, signing out, posting methods, and getting events.
Refers to Windows NT LanMan (NTLM) and Kerberos authentication over HTTP. The Unified Communications API supports this form of authentication for Microsoft Internet Explorer Internet browsers and AJAX clients for superior security and for allowing easy sign-in to Communicator Web Access Server by using cached credentials when a user has already logged on to a Windows domain.
Refers to actions performed by the Communicator Web Access Server at the request of a client. The request comes as a message in an XML format and is sent using an HTTP POST request. A method has a method name, a request ID, and one or more method parameters. Depending on the method, some parameters may be optional.
Without any modifiers, refers to a user login session or user session. A successful sign-in marks the beginning of a user session, which is identified by a unique session ID generated by the server and passed to the client with each response. The session ID is passed to the server with each further request to identify the session.
Logging on to a Communicator Web Access Server. This involves a client making an HTTP POST request to the server either by sending the user credentials with form-based authentication or by using integrated Windows authentication to perform the credential negotiation, followed by an initiateSession request.
Communicator Web Access Server supports this form of authentication for Microsoft Internet Explorer Internet browsers and AJAX clients for superior security and to allow easy sign-in to Communicator Web Access. The logon credentials are passed to subsequent servers so that the user does not have to supply their credentials again. For more information, see the Microsoft Office Communicator Web Access (2007) Authentication Guide.
This form of authentication requires two separate elements to successfully authenticate a user. Normally this is represented by (1) a smart card and smart card reader on a local user computer used in conjunction with (2) a user ID and password that a user enters on a logon form. The smart card has a PIN encoded that must match the PIN for the user in the Active Directory® store.
Application programming interface (API) to Communicator Web Access Server. The AJAX API is based on the AJAX programming model. This AJAX API consists of a set of methods and events. The methods are client requests to have something done: for example, querying the presence of a user, setting the presence of the caller, inviting a user to an instant messaging conversation, and so on. The events are the results of the method invocations and are returned to the client by the server. The methods and events use XML for their data format.