WebSocket Authentication on Client and Server #255
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
Remove the temporary directory and its contents to free up disk space
Add authentication for WebSocket connections. OAuth2PasswordBearer scheme from FastAPI security
Add authentication for WebSocket connection in Device class
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.
This pull request adds authentication functionality for WebSocket connections on both the client and server sides. The changes ensure that only authorized clients can establish a connection with the server.
Note: Make sure to define the WS_TOKEN variable in the environment variable file (e.g., .env) on both the client and server sides. The token should match on both sides for successful authentication.