Browser Session

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.

When a user first uses a Web browser to access the conference center user interface, a new browser session is created. Subsequent requests from the same user are associated with the browser session. When the user is authenticated, the user's credentials are associated with the browser session. The credentials, for example, enable an organizer to create several different meetings without having to provide a user password each time. The concepts apply to programmatic access using the Live Meeting service API.

For security, a browser session is automatically invalidated if it is inactive for a certain amount of time, known as the maxInactiveInterval. Inactive means that no request arrives that is part of the browser session. When a browser session is invalidated, the user's credentials are no longer available. Any request from the user that needs some privilege requires the user to authenticate again.

For example, suppose maxInactiveInterval is 30 minutes. An organizer signs in, walks away, comes back 31 minutes later, and tries to create a meeting. The organizer has to sign in again.

The value of maxInactiveInterval is available from GetConferencingServiceDataRequest and can be changed by SetConferencingServiceDataRequest.

This section uses the term browser session to distinguish it from the session established by an application that uses the Live Meeting service API.

See Also


Message Passing