feat(websocket): add authentication to websocket connection #345
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ramfox
force-pushed
the
ramfox/feat_websocket_auth
branch
from
4648225
to
cf7597c
Compare
b5
approved these changes
Sep 24, 2021
If we are already logged in, or have just successfully logged in, we need to authenticate our connection. This will let the backend know that it should send the events associated with the current session's profileID over the websocket connection. If we ever logout, we need to unsubscribe to this connection.
ramfox
force-pushed
the
ramfox/feat_websocket_auth
branch
from
cf7597c
to
481f0a7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #316
depends on qri-io/qri#1921