Cookies & Webex Meetings URL API

This section describes about third-party cookies and the Webex Meetings URL-based API.

Remember that when a host is logged in, either through the Webex Meetings interface or through the Webex Meetings API, a session cookie is created and attached to the browser instance. Session cookie is used to authenticate the host when they access Webex Meetings features or API calls are made. If there is a period of more than 30 minutes of inactivity, the cookie disables and the host must login again. If the host does not login again, they will receive the Access Denied message.

Because the Webex Meetings URL API uses a cookie, disabling third-party cookies have a negative impact on most, if not all, Webex Meetings API integrations. When accessing the Webex Meetings service directly from a Webex Meetings site, the session cookie is not considered as a potential threat, it is being written directly from the system to the host's computer. However, when the Webex Meetings service is accessed through an integration an interesting thing happens. Suddenly that helpful little cookie is looked as a potentially malicious threat to the host's computer because it is viewed as coming from a "third-party" source. This can cause a number of hard to diagnose problems, but it can be easily fixed without requiring the host to enable all third-party cookies by following these steps:

For IE 6+:

1. Click Tools from the menu bar.
2. Select Internet Options.
3. Click the Privacy tab.
4. Click the Edit button in the Web Site section (at the bottom).
5. Add webex.com in the Address of field and click the Allow button.
6. Click Ok.

For IE 5.5:

1. Click Tools from the menu bar.
2. Select Internet Options.
3. Click the Security tab.
4. Click Trusted Sites (green circle with white checkmark).
5. Click the Sites button.
6. Add webex.com in the Add this website to the zone field and click the Allow button.
7. Click OK.

If the Require Server Verification(https://) for all sites is selected, the full site name including the https:// information must be supplied.

Note: Many IT organizations have firewall/proxy configurations that block access for third-party cookies, JavaScript, ActiveX, etc. It is critical to the success of the integration that these groups are made aware of the requirement for Webex Meetings to be able to return information through client-server communication for a Webex Meetings URL-based API integration.

Community

Visit the Webex Developer Forum to ask questions and interact with other developers. Forums.

Twitter

Follow the Webex Developer program on Twitter for the latest industry and Webex Meetings related information. Follow us.