Hi Vineet,
I am not 100 % sure but I don't see why you could not reuse the same Redirect URL as soon as you will be back at the same page where the client start the Messenger
here some more document :
https://developer.genesys.cloud/blueprints/messenger-authentication-okta-integration-blueprint/
https://developer.genesys.cloud/commdigital/digital/webmessaging/messengersdk/authenticatedMessenger
regards
------------------------------
Frederic Thomas
Senior Manager, Development
------------------------------
Original Message:
Sent: 07-07-2025 03:33
From: Vineet Kakroo
Subject: Web Messaging Authentication Question
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
------------------------------
Vineet Kakroo
Senior Technical Consultant
------------------------------
Original Message:
Sent: 07-04-2025 12:54
From: Frederic Thomas
Subject: Web Messaging Authentication Question
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
------------------------------
Frederic Thomas
Senior Manager, Development