eparis | 2022-10-12 23:13:26 UTC | #1
Hello.
My team developed a web app that we then deploy as a Client Application Integration in Genesys (as a widget). The first thing this widget does is redirect the user to login in Genesys Cloud in order to generate an access token with the Code Authorization grant method. Because this is an embedded application (client application integration), it logs in with the same user that was used to log in to the Genesys dashboard. This is all correct and intended behaviour.
The web app was functioning properly as a widget. However, in our move to production we then deployed a new web app with all of the same code as the previously functioning web app and changed the configuration of the integration so that it would now embed this new url.
The login now doesn't work, displaying the following error (url of error and screen capture):
https://login.mypurecloud.com/#/error?errorKey=invalidClientId
We obviously thought that the mistake was somewhere in the redeployment of the web app. But we then tried a fix where we created new OAuth credentials for the application in Genesys (with the same configurations as the previous one) and changed the client id and client secret used by the app. This was the only change we did to the new app. This fixed the problem. The login now works.
We want to better understand the logic behind the Oauth clients in Genesys, why the error was happening in the first place, and why was the problem fixed by changing the Oauth client that had worked just fine for the old deployment of the app.
If you have any doubts, please ask. Thanks for any help you can give.
system | 2022-11-12 23:14:21 UTC | #2
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 16701