Hi Genesys team, I have some doubts about the implementation of the authentication step in web messaging.
I am considering how to do authentication in the backend, indicating a client id and secret to follow the openid standard with Google. But I am not sure what type of credentials I would have to use from the backend to be able to do this, since if I use the client type they are linked to an email (which has to accept the conditions, etc.) and in my case it is the backend who is performing this authentication, could you give me some guidance on how I could resolve this part?
Hi - did you follow guidance here? Get started with authenticated web messaging - Genesys Cloud Resource Center
Note that you have to obtain client-id and client-secret from your Google Cloud Platform console: when you create and save a new OAuth Client, that will also generate your client-id & client-secret values. There is no email address involved.
Hi
Yes, I have followed these steps and I have configured it, and I also did these steps to generate the new OAuth Client in google.
But if I am understanding correctly when using this type of credentials, when I try to obtain the auth code the Google consent window will appear and this is something that would not make sense to do from the backend.
The Google consent window will appear to your End-Users (if they want to use Authenticated Web Messaging, they have to sign-in): upon successful sign-in, the Authorization Code is captured on the web client and passed into Web Messaging APIs. Genesys Cloud backend will then use OAuth credentials to validate the Authorization Code against Google APIs: there is no further consent at this step, as this happens via OAuth credentials, not User credentials.