Cisco Systems Conference Phone manual Terms of Support for Single Sign On Software Integration

Chapter 1 Introducing Cisco Unified MeetingPlace Web Conferencing Release 5.3

Terms of Use

•CPE customers who want to integrate SSO packages can contact Cisco Managed Services to obtain a Service Request to implement SSO. This service is offered as a convenience and does not change the scope of the SSO integration: this service is an integration and configuration of the Cisco Unified MeetingPlace Web Conferencing product, not a customization of the product code.

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

•Customers are responsible for ensuring stability of integrated Cisco Unified MeetingPlace 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. Cisco Unified MeetingPlace Web Conferencing installs and uses four IIS extensions. Any incompatibility between an SSO software extension and the Cisco Unified MeetingPlace 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 Cisco Unified MeetingPlace Web Conferencing outage, resulting in a full system restart, ending of in-progress meetings, and disconnecting of web-conferencing users. Any memory leak in the SSO package or module can make IIS or the whole server unstable, as well.

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

Terms of Support for Single Sign On Software Integration

•Customers must inform Cisco TAC that their Cisco Unified MeetingPlace Web Conferencing servers have third-party SSO packages installed and configured with Cisco Unified MeetingPlace Web Conferencing when opening a service request for Cisco Unified MeetingPlace Web Conferencing, Cisco Unified MeetingPlace for Microsoft 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 if the problem is on the SSO side or the Cisco Unified MeetingPlace 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 Cisco Unified MeetingPlace Web Conferencing problem that does not seem to be connected to the SSO integration, Cisco TAC will proceed per the normal support process. If 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.

•Microsoft Debug Diagnostic tool, also called DebugDiag, may be required for troubleshooting IIS crashes and memory leaks to determine if these problems are produced by the SSO package.

Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3

OL-10029-01 1-3