Cisco Cisco Unified MeetingPlace Web Conferencing

By allowing SSO software integrations, we do not claim support for any SSO software packages or 
vendors. 

SSO software integrations require proper configuration of Web Conferencing systems through the 
Admin pages. If the SSO software integration requires a change in the Web Conferencing product 
source code, the SSO integration becomes an SSO customization, and we do not support 
customizations by either customers or any other parties. 

CPE customers who want to integrate SSO packages can contact Cisco Managed Services to obtain 
a service request for implementing SSO. The service is offered as a convenience and does not change 
the scope of the SSO integration; the service is an integration and configuration of the Web 
Conferencing product, not a customization of the product code.

Customers must first implement SSO software integrations on test or lab servers and confirm that 
the integrated systems work, including Web Conferencing features and operations.

Customers are responsible for ensuring stability of integrated Web Conferencing-SSO systems, 
including communicating with SSO software vendors for the following reasons: 

To obtain necessary fixes and support.

To troubleshoot functional problems and technical problems, including crashes triggered by the 
SSO package.

SSO software often includes a web-server extension, called the IIS ISAPI extension or filter. Web 
Conferencing installs and uses four IIS extensions. Any incompatibility between an SSO software 
extension and the Web Conferencing extensions can make IIS non-functional or unstable. Any crash 
of the SSO IIS extension can cause IIS to crash and can generate a full Web Conferencing outage, 
resulting in a full system restart, termination of in-progress meetings, and disconnection of 
web-conferencing users. In addition, any memory leak in the SSO package or module can make IIS 
or the whole server unstable.

Although SSO software integration is productized for the Web Conferencing system, any changes 
in overall configuration, including Web Conferencing upgrades and SSO package upgrades, can 
potentially break integrated Web Conferencing-SSO systems.

Customers must inform Cisco TAC that their Cisco Unified MeetingPlace Web Conferencing 
servers have third-party single sign-on (SSO) packages installed and configured with Web 
Conferencing when opening a service request for Web Conferencing, Cisco Unified MeetingPlace 
for Outlook, or Cisco Unified MeetingPlace for Lotus Notes.

Customers must be able to provide SSO integration details upon request. Inability to provide details 
can result in Cisco TAC not being able to proceed with service requests.

If a service request is about troubleshooting the SSO integration, Cisco TAC can review the logs and 
identify whether the problem is on the SSO side or the Web Conferencing side. If the problem is on 
the SSO side, information will be provided to customers, so they can further troubleshoot with their 
SSO vendors.

If the service request is about troubleshooting a Web Conferencing problem that does not seem to 
be connected to the SSO integration, Cisco TAC will proceed per the normal support process. If 
Cisco TAC discovers that the SSO integration plays a role in the problem, information will be 
provided to customers, so they can further troubleshoot with their SSO vendors.

If Cisco TAC believes the problem is triggered by an SSO package, Cisco TAC can require 
customers to disable the SSO package to troubleshoot further.