I need some assistance with login-logout flow with OAuth login flow.
As the user I want:
1. Login with one account.
2. Logout
3. Login with a different account
In the steps hire in code I use:
1. rcsdk.loginWindow and than make rcsdk.login (popup open, user login, it's okay)
2. rcsdk.logout
3. the same as 1 step
In the step 3 user see in pop up window 'Continue as' first account he used, it will not require any password.
Is there any way I can after logout in the new login not show user information about his previous login, just clean login?
Will appreciate your help on that.
Best answer by Anonymous
When you log in using OAuth, the session cookies are stored in the browser when you are redirected to the RingCentral auth page and successfully log in. There is also your use case where multiple users might be using the same machine and browser instance to log into the app where the cookies will not be deleted by default. From what I know, the SDK does not have such an option to force deleting the cookies.
There are 2 things you can do that I can think of right now
1. Make sure the logged-in user closes the browser after login. Closing the browser instance after they are done working should (from what I know) clear the cookies. That being said, this is a manual task
Did this thread help you find an answer to your question?
2 replies
A
Anonymous
0 replies
April 19, 2022
@Polina Zubova The session details are saved in the cookie in the browser once the user logs in Is your use case where multiple users can log in from the same browser on the same machine? If that is not the case, any other user trying your app will still see a login screen since their browser cookie will not be set
A
Anonymous
0 replies
Answer
April 20, 2022
When you log in using OAuth, the session cookies are stored in the browser when you are redirected to the RingCentral auth page and successfully log in. There is also your use case where multiple users might be using the same machine and browser instance to log into the app where the cookies will not be deleted by default. From what I know, the SDK does not have such an option to force deleting the cookies.
There are 2 things you can do that I can think of right now
1. Make sure the logged-in user closes the browser after login. Closing the browser instance after they are done working should (from what I know) clear the cookies. That being said, this is a manual task
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
