Genesys Cloud Messenger Lab

Load any Messenger deployment, detect authenticated messaging, and test a standards-based OpenID Connect authorization-code flow with optional PKCE.

Checking browser context Deployment not loaded Auth unknown

Messenger deployment

Choose the Genesys Cloud region and enter the deployment ID.

Genesys Cloud environment Region

Deployment ID UUID

Current page origin Add this to the deployment's allowed domains

Advanced bootstrap overrides

Apps domain override Optional

Bootstrap environment override Optional

Enable Genesys bootstrap debug mode

OpenID Connect authentication

Shown because authentication is enabled on the Messenger configuration.

Not signed in

No client secret is requested here. For the normal authorization-code Messenger flow, keep the secret in the Genesys OpenID Connect Messenger Configuration integration. This page only obtains the short-lived authorization code and, when selected, the PKCE verifier.

Client ID OIDC application

Auth flow Authorization Code

IDP URL / Issuer / Discovery URI OIDC

Authorization endpoint Auto-discovered; manual fallback supported

Redirect URI Must exactly match the IDP registration

Token age / max_age Seconds; optional

Prompt Optional OIDC parameter

Response mode Optional

Additional scopes Space separated

Scopes openid is mandatory for OIDC

openid profile email offline_access phone

Additional authorization parameters One key=value per line

OIDC discovery information

Discovery URI

Issuer

Authorization endpoint

Token endpoint

PKCE methods

Runtime status

Live state from the Messenger deployment and AuthProvider.

Region

Bootstrap

Deployment ID

Messenger ready

Authentication enabled

Unknown

OIDC callback code

None

AuthProvider state

Unknown

Diagnostics

Useful for deployment, OIDC, PKCE, and Messenger authentication troubleshooting.

0 events

Test checklist

Conditions that commonly prevent authenticated Messenger from working.

1. Serve this page over HTTPS or localhost. Do not open it directly as a local file for OIDC testing.

2. Add this page origin to the Messenger deployment's allowed domains.

3. Use the same OIDC client configuration expected by the Genesys OpenID Connect Messenger Configuration integration.

4. The redirect URI must match exactly in the authorization request, IDP app registration, and the value passed to Messenger.

5. If max_age, nonce, PKCE, or iss is used in the authorization request, keep the corresponding values consistent when Messenger exchanges the authorization code.