Hello Community,

I have a question about web messaging authentication process.
We are not sure what we are missing.

Our customers login to our website and we authenticate the login via an existing OIDC provider for this. Once they login to the website, they then have the option to initiate the web-message. This is where we are not sure what is required from us to get the web-message into authentication state. As we have already logged into our website authenticated, how can we get the web-message use the same authenticated session, or do we need to do a second authentication with OIDC provider. The same OIDC provider is setup on Genesys Cloud and all messaging setup are complete.

Based on the web-messaging examples and documentation, we don't seem to understand what we are missing.

Any help would be really helpful.

Regards

Hi Vineet, 

you need to reauthenticate user and provide to the plateform the code. 

At the moment the Web Messaging authentication is supporting only the Authorization code flow . 

https://developer.genesys.cloud/commdigital/digital/webmessaging/authenticate

We are working to support implicit flow that allow you to pass an id_token based on your website authentication . It should be released later this year

regards

Hello Community,

I have a question about web messaging authentication process.
We are not sure what we are missing.

Our customers login to our website and we authenticate the login via an existing OIDC provider for this. Once they login to the website, they then have the option to initiate the web-message. This is where we are not sure what is required from us to get the web-message into authentication state. As we have already logged into our website authenticated, how can we get the web-message use the same authenticated session, or do we need to do a second authentication with OIDC provider. The same OIDC provider is setup on Genesys Cloud and all messaging setup are complete.

Based on the web-messaging examples and documentation, we don't seem to understand what we are missing.

Any help would be really helpful.

Regards

Thanks Frederic.

One more question, in our case as mentioned, when we do our first login to the website, we have a redirect URL that we pass onto the authentication server. This works fine. Now if we have to do a reauthentication specifically for Genesys using a different clientid/secret/redirectURL, we are not sure what the redirect URL will be in this case as I am sure we can't be having the same redirect URL as we had before for a normal website login. Does the redirect URL need to be localhost or something else ?

Regards

Hi Vineet, 

you need to reauthenticate user and provide to the plateform the code. 

At the moment the Web Messaging authentication is supporting only the Authorization code flow . 

https://developer.genesys.cloud/commdigital/digital/webmessaging/authenticate

We are working to support implicit flow that allow you to pass an id_token based on your website authentication . It should be released later this year

regards

Hello Community,

I have a question about web messaging authentication process.
We are not sure what we are missing.

Our customers login to our website and we authenticate the login via an existing OIDC provider for this. Once they login to the website, they then have the option to initiate the web-message. This is where we are not sure what is required from us to get the web-message into authentication state. As we have already logged into our website authenticated, how can we get the web-message use the same authenticated session, or do we need to do a second authentication with OIDC provider. The same OIDC provider is setup on Genesys Cloud and all messaging setup are complete.

Based on the web-messaging examples and documentation, we don't seem to understand what we are missing.

Any help would be really helpful.

Regards