HI Mihail,
Sorry I misunderstood your question and didn't look at the right step you pointed out.
This schema is a bit simplify one : we are checking if the user token/code checked against OIDC is expired or not :
- If not and JWT provided is matching, we are validating the session. (to reduce call to OIDC server)
- Else we could using the refresh token mechanism to see if the user session is still valid from OIDC side
I hope I address your point
regards
------------------------------
Frederic Thomas
Senior Manager, Development
------------------------------
Original Message:
Sent: 01-19-2026 07:42
From: Mihail Ivanov
Subject: Session validation with Third party auth provider - How does it happen - Authenticated web messaging
Hi Frederic,
I understand how the authentication works in the beginning of the flow.
My question is how specifically is the authentication server queried about the validity of the session, after authentication has already happened?
Which endpoint is being called here to check whether the already issued token is valid?
Kind regards,
Mihail Ivanov
------------------------------
Mihail Ivanov
------------------------------
Original Message:
Sent: 01-16-2026 12:32
From: Frederic Thomas
Subject: Session validation with Third party auth provider - How does it happen - Authenticated web messaging
Hi Mihail,
you need to create a specific integration in Genesys Cloud as describe here https://developer.genesys.cloud/blueprints/messenger-authentication-okta-integration-blueprint/#create-an-oauth-integration-in-genesys-cloud . It's rely on the OIDC application that you configure on your side
This integration will have to be used in the WebMessaging Deployment .
The authentication server will check that the code provides by the custom application is a valid code and it will allow to retrieve all claims from this user
I hope it's clarify the workflow
regards
------------------------------
Frederic Thomas
Senior Manager, Development