Thank you for the clarification and for taking the time to review this.
It's helpful to know that reloading the iframe is not required by design to enable Framework Client tokens.
We'll proceed with opening a ticket with Genesys Customer Care to investigate this further on our environment.
Thanks again for your guidance.
Original Message:
Sent: 01-30-2026 10:15
From: Junji Sawada
Subject: OAuth error with "enableFrameworkClientId" in Genesys Embeddable Framework – is iframe reload the only solution?
Thank you for the additional explanation.
Reloading the iframe should not be necessary to enable Framework Client tokens if everything is set up correctly.
If you are still encountering the error message after using the correct OAuth client ID and redirect URI, I would recommend to contact Genesys Customer Care and open a ticket with them. We do not have access to customer environments, logs and data from the forum. Support may be able to give you more details about what they see on their end.
Regards,
------------------------------
Junji Sawada
Senior Software Engineer, Team Lead
------------------------------
Original Message:
Sent: 01-29-2026 21:05
From: Katsuya Watabe
Subject: OAuth error with "enableFrameworkClientId" in Genesys Embeddable Framework – is iframe reload the only solution?
Thanks for the suggestion.
We tested again using an OAuth client with Implicit Grant only:
- Removed
usePKCEAuthFlowfrom the framework settings - Confirmed the Embeddable Framework integration was updated
- Loaded the iframe with
enableFrameworkClientId=trueon the initial load
However, we are still seeing the same error:
"Sorry, Genesys Cloud cannot authenticate you at this time.
The OAuth client ID or redirect URI is invalid"
Based on this result, the issue does not appear to be related to PKCE,
but rather to usingenableFrameworkClientId=trueduring the initial iframe load.
The current workaround we are using
(loading the iframe withoutenableFrameworkClientIdfirst,
then reloading the iframe after the login session is established)
works as expected.
This workaround behaves consistently regardless of the OAuth flow type
(PKCE or Implicit).
Please let us know if there is an officially supported way to enable the Framework Client without reloading the iframe, or if this behavior is expected by design.
------------------------------
Katsuya Watabe
Original Message:
Sent: 01-29-2026 16:01
From: Junji Sawada
Subject: OAuth error with "enableFrameworkClientId" in Genesys Embeddable Framework – is iframe reload the only solution?
The `usePKCEAuthFlow` setting is not supported yet (see the Feature postponement announcement at the top of this documentation).
Please try again using an appropriate OAuth client grant type without the `usePKCEAuthFlow` setting to see if that make a difference. Thank you.
------------------------------
Junji Sawada
Senior Software Engineer, Team Lead