Support multiple bridge clients per server#18
Draft
yzx9 wants to merge 1 commit into
Draft
Conversation
Bridges authenticate by sending an "auth" WebSocket message after ID negotiation. The server maps access tokens to client IDs so the web frontend can route requests to specific bridges. The Settings UI now has a Bridge tab with a client selector dropdown and access token input.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
authevent after connecting, allowing the server to identify and route requests to specific clientsAuthorization: Bearer <token>for the server to resolve the target bridge