Skip to content

Commit 33a9aae

Browse files
docs: distinguish browser WebSocket authentication
1 parent af04aae commit 33a9aae

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

‎docs/internals/environment-auth.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,10 @@ rather than fall back to bearer authentication. The OAuth token-exchange
2424
vocabulary gives these grants a familiar meaning, but the environment does not
2525
implement a general-purpose OAuth authorization server.
2626

27-
WebSockets use short-lived tickets obtained through authenticated HTTP so
28-
long-lived credentials stay out of socket URLs. A successful handshake grants
29-
no extra authority: [every RPC declares a required
27+
Bearer and DPoP clients obtain short-lived WebSocket tickets through authenticated
28+
HTTP so long-lived tokens stay out of socket URLs. Browser sessions can
29+
authenticate the upgrade with their cookie. A successful handshake grants no
30+
extra authority: [every RPC declares a required
3031
scope](../../apps/server/src/auth/RpcAuthorization.ts).
3132

3233
Desktop restarts forget the previous local bearer token, so its reusable

0 commit comments

Comments
 (0)