Does the OIDC flow (step 1) have to be initiated by a client-side application? In other examples of OIDC, typically the interaction is initiated by the 3rd Party/SaaS provider and then the same platform also does the auth code exchange for access tokens. We are not sure if our OIDC IDP can support having the interaction split, but we could experiment if that is the only pattern available.
The 3rd Party / SaaS providers (Genesys Cloud in this case) would need "some event" to start the OIDC flow, which is typically triggered by the End-User's state (either new sign-in attempt or already signed-in status).
The standard OIDC flow described is the "Authorization Code Flow", so somehow your App needs to retrieve the Authorization Code from IdP, and make that available to Genesys Cloud.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.