Skip to content

fix(supabase): don't send Authorization on the realtime upgrade - #622

Merged
Tr00d merged 1 commit into
supabase:masterfrom
fresh55:fix/realtime-upgrade-authorization
Nov 2, 2026
Merged

Tr00d merged 1 commit into
supabase:masterfrom
fresh55:fix/realtime-upgrade-authorization

Conversation

@fresh55

@fresh55 fresh55 commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

With a session, the client sent the user JWT as Authorization on the realtime websocket upgrade, and hosted Realtime answers 401 for it. The token already reaches Realtime through SetAuth and the channel join, so the header is dropped for Realtime only.

Closes #619

@Tr00d
Tr00d merged commit f9bf4a3 into supabase:master Nov 2, 2026
6 checks passed
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 this pull request may close these issues.

Realtime WebSocket upgrade returns 401 for a user JWT accepted by Auth

2 participants