LighthouseMike | 2022-12-21 19:50:21 UTC | #1
Okay, so a similar question was asked around 2017, and the answer was in the docs (here's the current docs, to redirect to the Genesys logout page. That's all well and good, but if the user wants to log back into our system (not the default) the "redirect_uri" parameter isn't working. I've tried a few variations...
encodeURI("https://login.usw2.pure.cloud/logout?client_id=<my_clientID>&redirecturi=" + location.href); "https://login.usw2.pure.cloud/logout?client_id=<my_clientID>&redirecturi=" + encodeURIComponent(location.href); // etc.
And so far, none of it seems to work. Specifically, they log me out, but then logging back in goes to the default GUI, not my redirect link (which is on the list in the API settings). The only way to get back into my project after logging out is by re-typing/re-pasting the URL in the address bar.
I also tried with that other URL (purecloud.com or whatever it was in the docs) and I don't remember what that did except that it didn't seem to be much. If I remember correctly it didn't log me out of Genesys (cuz I think that's... what is it, west coast? east coast? lol idk u guys have so many locations). I could be way out in left field on that one lol...
Anyway, how would I go about debugging this? It's all redirects, so it's not like I can use PHP error_log or JS console.log or something... WireShark maybe? :laughing: Okay seriously, I've never had to debug redirects-in-progress before so maybe this is a super-noobish question with a simple answer. Hope so anyway. :smiley:
tim.smith | 2022-12-21 21:33:31 UTC | #2
If you need assistance looking into what's happening behind the scenes, please open a case with Genesys Cloud Care to investigate. Those of us on the forum don't have access to see your org's configuration and have limited access to logging. Auth processes are purposefully opaque for security purposes. My guess is that your redirect URI doesn't match exactly, character for character, with the redirect URI that's configured for the client.
LighthouseMike | 2022-12-22 14:21:35 UTC | #3
I get that we don't want to log stuff that would clue hackers in on how stuff works, and I get that the redirect URL has to be an exact match, but the docs leave out some info (also by design?) that I think would help me debug on my end:
- Is the base part of the URL (my.pure.cloud or purecloud.whatever) always the same regardless of which location you're normally sending API requests to?
- Does the redirect URL have to be encoded (i.e. space to %20?
- An example or two would be helpful.
If I can check against the docs to make sure I'm doing things correctly, and the issue persists, then I would bug our sysadmin to get in touch with your support team or whatever. Not sure if I should submit that as a feature request or what, but the limited info on how to do it right doesn't help. Regardless, glad to know that we can get with your support team and it's not just this forum. :smiley:
Anyway, have a great day, a merry Christmas (or happy Hanukkah, or happy holiday or whatever) and I will "see you next year". :smile:
tim.smith | 2023-01-04 15:08:32 UTC | #4
LighthouseMike, post:3, topic:17738
Is the base part of the URL (my.pure.cloud or purecloud.whatever) always the same regardless of which location you're normally sending API requests to?
No, you must always use the endpoints for your org's region.
LighthouseMike, post:3, topic:17738
Does the redirect URL have to be encoded (i.e. space to %20?
Query parameter values should always be encoded; this is not specific to Genesys Cloud (RFC 2396 section 2.2.
LighthouseMike, post:3, topic:17738
An example or two would be helpful.
The documentation contains an example logout URL: https://developer.genesys.cloud/authorization/platform-auth/#logging-out---destroy-all-associated-tokens. What specifically are you looking for beyond this example of the logout URL's format?
LighthouseMike | 2023-01-04 15:08:24 UTC | #5
Just the questions you just answered. :smiley: Thank you.
system | 2023-02-04 15:09:10 UTC | #6
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: 17738