My software has always used the following URL to logon a user "https://login.usw2.pure.cloud/authorize?client_id={ClientId}&response_type=token&redirect_uri={RedirectUri}" and the following URL to logoff a user "https://login.usw2.pure.cloud/logout". A month or two ago something changed and I haven't gotten to address it until now. It used to be that a user would logon to the phone switch (using the URL above), then logoff the phone switch (using the other URL above) and then the next time they logged into the phone switch (using the URL above) they would be prompted for their user/pw again. But a month or two ago the behavior changed so that the second time they logged into the phone switch it would NOT prompt them for a user/pw. Instead it would remember who was logged in on that machine previously and just log them in again without prompting for a user/pw. Is there something else/different I need to do now when I log a user off so that the next time they login on that machine (even if it is 5 seconds later) it will prompt them for user/pw again instead of just logging them in as the last user who logged in on that workstation?
https://login.usw2.pure.cloud/logout is still the correct way to destroy the user's session for the context in which the page was accessed (i.e. the specific browser session that navigates to that URL). This destroys the session cookie that allows logging in automatically for future requests. If this page is not working, please open a case with Genesys Cloud Care to report the issue.
Got it will do. Is there a cookie I can manually delete that will have the same effect? Rarely the software will lockup and they kill it through taskmgr. I would like to delete the cookie before logging them in just to catch that scenario if that is a viable solution.
The cookie isn't on your domain and doesn't support cross-domain access, so your application can neither read nor delete it.
Update just for informational purposes for anyone interested in this issue. It turns out the issue was in my software. I have a form with a web browser control that is used to navigate to the login/logoff pages respectively. Although it is the same form and control for both calls, my architecture had changed slightly so that it was a different thread making the logoff navigation request than originally made the login navigation request. Apparently you need to have the same processing thread make the logoff navigation call as made the login navigation call. When I made that change (using delegate sub to force the UI thread to handle the request) it all started working again.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.