Genesys Cloud – Deprecation: Restrict URLs from accessing browser cookies, local storage, and JavaScript APIs

To reduce potential security risks associated with embedded external content, Genesys is updating how the Web Content URL widget functions within Genesys Cloud Analytics dashboards. Specifically, Genesys will restrict URLs from accessing browser cookies, local storage, and JavaScript APIs. This change applies to URLs originating from the same origin or host and that rely on JavaScript-based interactions. On the effective date, any URLs that depend on these capabilities will be restricted and may no longer load or function as expected within the widget.

FAQs

Am I affected?

You are affected if your dashboard widgets include configured URLs that rely on access to browser cookies, local storage, or JavaScript APIs to render or function correctly.

What do I need to do before the effective date?

Review all Genesys Cloud Analytics dashboards that use the Web Content URL widget. If any configured URLs depend on cookies, browser local storage, or JavaScript APIs, update them as needed to ensure uninterrupted functionality.

To ensure continued functionality, perform the following before the effective date:

1. Identify dashboards that include the Web Content URL widget.
2. Evaluate the configured URLs to determine whether they rely on cookies, local storage, or JavaScript APIs.
3. Replace or update any dependent URLs with alternative URLs that do not require restricted browser capabilities.
4. Verify that each widget loads correctly and displays the expected content after updates are applied.

How to validate URL dependencies on local storage, including cookies, browser storage, or JavaScript APIs?

Open the dashboard that contains the web URL widget in an incognito or private browsing session. If the dashboard loads as expected, the widget is unlikely to be impacted and no action is required.

If the dashboard does not load correctly, this indicates a dependency on local storage. In such cases, update the URL configured in the widget to one that functions correctly in incognito mode.

What happens after the effective date?

After the effective date, URLs that rely on cookies, browser local storage, or JavaScript APIs will be restricted and may no longer function as expected within the Web Content URL widget.

What if I need help or have questions?

Contact My Support for assistance.