You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f6e4fd4
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(client-runtime): decide learned routes and session reuse in one place
Learned routes only take a plain-HTTP address off the tailnet when the paired
credential they borrow was itself paired over plain HTTP to a LAN or public
address. A token paired over HTTPS, loopback, or the tailnet keeps to the
transports it was issued for. Relay credentials are unaffected.
SSH reconnects reuse their existing session instead of creating a new one. The
SSH route's bearer token is now saved in the connection catalog, the resolver's
SSH broker passes it to the gateway and saves whatever comes back, and the
desktop gateway checks the saved session against the host (valid and holding
every standard client scope) before reusing it. It pairs again only when the
session is rejected or lacks a scope, and stops without pairing or sending the
token when the forward reaches a different environment. Adding an environment
and its first connect share one session, and removing the route drops the
token.
Docs: docs/user/remote-access.md describes one session per desktop and how to
revoke unused ones; docs/internals/remote.md notes the plain-HTTP rule for
learned routes.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments