Allows unauthenticated attendees to enter an unlocked room if they have signed in within the last few weeks in classic view.

This site administrator option is now retired and can’t be enabled through the user interface.

Stores a unique CSRF (Cross-Site Request Forgery) token to help protect against CSRF attacks.

Webex checks each request for a valid token and rejects any requests with a missing or incorrect token value.

Stores the CDN (Content Delivery Network) host endpoint and health status to support source file, package, and library downloads.

This cookie helps detect CDN server status and doesn’t store any sensitive information.

Maintains session state information across a series of requests from the same user and browser over time.

Generates a unique meeting authentication token to encrypt and decrypt tokens when adding webinar materials.

Stores the attendee’s user name and email after sign-in or CAPTCHA verification when joining a classic Personal Meeting Room (PMR). This applies when the site administrator enables the Show CAPTCHA when attendees enter a host's Personal Room option.

The cookie allows unauthenticated users to bypass CAPTCHA if they have previously signed in or joined a PMR and selected Remember Me.

Stores the attendee’s first name, last name, and email address after their last sign-in or when they join an Event Center (EC), Training Center (TC), or classic Personal Meeting Room (PMR). This occurs when the attendee selects Remember me on this computer.

For unauthenticated users, the cookie provides an auto-filled experience for the first name, last name, and email when joining EC, TC, or classic PMR after selecting Remember me on this computer.

Stores the attendee’s first name, last name, and email address after their most recent meeting registration or webcast meeting, and if they select Remember me on this computer.

For unauthenticated users, this cookie auto-fills the first name, last name, and email fields when registering for a meeting or joining a webinar.

Stores the user’s cookie consent preferences to determine whether functional and performance cookies are allowed. Without this cookie, the cookie preference mechanism can’t function properly. For example, the CookieConsentOption may record values such as {"functionalValue":0,"performanceValue":1}.

Stores the user’s language preference for page display.

For authenticated users, the cookie saves their personal language setting. For unauthenticated users, it saves the site’s default language setting.

Stores the user’s region preference for page display.

For authenticated users, the cookie saves their personal region setting. For unauthenticated users, it saves the site’s default region setting.

Stores the user’s timezone preference for page display.

For authenticated users, the cookie saves their personal timezone setting. For unauthenticated users, it saves the site’s default timezone setting.

Stores the preferred language for page display.

For authenticated users, the cookie saves the user’s language setting. For unauthenticated users, it saves the site’s default language setting.

Stores the preferred region for page display.

For authenticated users, the cookie saves the user’s region setting. For unauthenticated users, it saves the site’s default region setting.

Stores the preferred timezone for page display.

For authenticated users, the cookie saves the user’s timezone setting. For unauthenticated users, it saves the site’s default timezone setting.

Stores a unique guest ID to ensure that each browser and meeting session is associated with a single guest identifier.

This helps support telemetry and tracking.

Stores the wbxsid in the browser to cache user information during recording playback.

This cookie allows users to refresh the page without needing to re-enter their password or registration details.

Stores a hash value for the kubed pod to maintain session stickiness. This ensures that all requests for a particular session are routed to the same physical machine that handled the initial request.

By doing so, the cookie prevents loss of in-process session data caused by requests being routed to different servers.

Stores meeting template information when the user selects or saves a meeting template.

When the user visits the scheduling page, Webex considers the template stored in this cookie. If the cookie isn’t present, Webex displays the user’s default meeting template from the backend.

Stores the global URL for User Hub.