Legacy Dev Forum Posts

 View Only

Sign Up

Allowing chrome-extension://... or https://${EXTENSION_ID}.chromiumapp.org/ Origins

  • 1.  Allowing chrome-extension://... or https://${EXTENSION_ID}.chromiumapp.org/ Origins

    Posted 06-05-2025 18:33

    TalkingScientist | 2025-03-01 09:40:04 UTC | #1

    I’m building a Chrome extension that uses the Genesys Cloud Implicit Grant flow. The extension successfully acquires an OAuth token, but when it calls the /api/v2/conversations/calls endpoint, the request is blocked by CORS. It looks like Genesys Cloud isn’t returning Access-Control-Allow-Origin for my extension’s origin (chrome-extension://<EXTENSION_ID> or https://${EXTENSION_ID}.chromiumapp.org/).

    The same code works fine from a regular HTTPS domain, so I know my payload is valid and my credentials/scopes are correct. Is there a recommended way to configure Genesys Cloud (or the OAuth client) so that calls from a Chrome extension are allowed? Any best practices for enabling Access-Control-Allow-Origin for a chrome-extension:// or https://${EXTENSION_ID}.chromiumapp.org/ origin would be greatly appreciated.


    system | 2025-03-31 09:40:09 UTC | #2

    This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 31983