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]: unauthorize open connections #145

Closed
2 tasks done
lennartkloock opened this issue Nov 10, 2023 · 0 comments · Fixed by #158
Closed
2 tasks done

[Feature]: unauthorize open connections #145

lennartkloock opened this issue Nov 10, 2023 · 0 comments · Fixed by #158
Labels
bug Something isn't working

Comments

@lennartkloock
Copy link
Member

Tell us about your Wish

We need to unauthorize open connection when their session or user gets deleted. They stay authorized right now. (Look at the password mutation query)

Is your feature related to a bug

No response

Alternatives

No response

Additional Info

No response

Participation

  • I am willing to submit a pull request to implement this

Disclaimer

  • I agree
@lennartkloock lennartkloock added bug Something isn't working backend labels Nov 10, 2023
@lennartkloock lennartkloock added this to the Initial Launch v1.0.0 milestone Nov 10, 2023
TroyKomodo added a commit that referenced this issue Nov 24, 2023
Since websocket connections live longer, auth might have expired before
the request so we need to validate auth at every call, rather than just
at the start.

fixes #145
@TroyKomodo TroyKomodo mentioned this issue Nov 24, 2023
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant