Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Logout or Invalidate Auth/Refresh token through Nakama backend #1014

Open
abmaurya opened this issue Apr 13, 2023 · 1 comment · May be fixed by #1175
Open

[Feature Request] Logout or Invalidate Auth/Refresh token through Nakama backend #1014

abmaurya opened this issue Apr 13, 2023 · 1 comment · May be fixed by #1175

Comments

@abmaurya
Copy link

abmaurya commented Apr 13, 2023

Using single_socket makes sure that there’s only one active sessions by disconnecting the previous login. The problem with this solution is that single_socket only disconnects socket, does not log out the user from that other device(previous login). This could pose as a security flaw as the auth token and refresh token are still valid.
There should be a way to invalidate these tokens(tokens from older login) or simply log out the older login maybe through a configuration along side single_socket on the backend.

Forum discussion:

My comment:
https://forum.heroiclabs.com/t/preventing-users-from-having-multiple-sessions/36/13

Chris Molozian's comment:
https://forum.heroiclabs.com/t/preventing-users-from-having-multiple-sessions/36/14

Chris has provided a solution in the above comment but that is still not secure because it is not Nakama authoritative which would be the most secure scenario.

@abmaurya abmaurya changed the title [Feature Request] Logout or Invalidate Auth/Refresh token through Nakama [Feature Request] Logout or Invalidate Auth/Refresh token through Nakama backend Apr 13, 2023
@UmarBhatPlaystrom
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants