Genesys Cloud - Developer Community!

The Authenticated Web messaging flow outlined here https://developer.genesys.cloud/commdigital/digital/webmessaging/authenticate has a step to validate the session with the Authentication Server, namely step 14 (and 15). Since this step is not part of the mandatory specification of either OAuth 2.0 or OpenID Connect, it is currently unclear to me what exactly is done here by the Genesys Cloud platform.

My question is, what happens in step 14 (and 15) and how is the Authentication Server expected to accommodate this? Is it an API endpoint that needs to be available or some other mechanism that needs to be configured?

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

The Authenticated Web messaging flow outlined here https://developer.genesys.cloud/commdigital/digital/webmessaging/authenticate has a step to validate the session with the Authentication Server, namely step 14 (and 15). Since this step is not part of the mandatory specification of either OAuth 2.0 or OpenID Connect, it is currently unclear to me what exactly is done here by the Genesys Cloud platform.

My question is, what happens in step 14 (and 15) and how is the Authentication Server expected to accommodate this? Is it an API endpoint that needs to be available or some other mechanism that needs to be configured?

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

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

The Authenticated Web messaging flow outlined here https://developer.genesys.cloud/commdigital/digital/webmessaging/authenticate has a step to validate the session with the Authentication Server, namely step 14 (and 15). Since this step is not part of the mandatory specification of either OAuth 2.0 or OpenID Connect, it is currently unclear to me what exactly is done here by the Genesys Cloud platform.

My question is, what happens in step 14 (and 15) and how is the Authentication Server expected to accommodate this? Is it an API endpoint that needs to be available or some other mechanism that needs to be configured?