Signing in as a person
trino --external-authentication (or any OAuth2-aware Trino client) opens a browser to your
tenant’s sign-in page. Consent names one capability: “Run SQL on your tenant’s data”
(query_engines:execute_sql). Once you approve, the coordinator holds your session and renews it
for you — neither how long a query takes nor how long you spend paging through results is bounded
by a single token’s lifetime. See Connect to an engine for the exact command.
Machine access
A scheduled job has no browser, so it uses a different grant: a service user’s API key, exchanged for a token bound to one engine (RFC 6749 client-credentials). The token’s lifetime is a fixed window rather than something the coordinator renews — long enough for a batch job, not indefinite — so a very long-running scripted job should be sized with that ceiling in mind. See Connect to an engine for the exchange itself, and Service users and API keys for minting the key.A machine token is never re-issued a refresh token. If a script’s work might outlast the token, have
it re-exchange the API key rather than assume the credential renews itself.
Web UI sign-in
The console’s own SQL surfaces (the workbench, catalog browser) sign you in the same way behind the scenes — you don’t see a separate OAuth prompt, because you’re already signed in to your tenant.Revocation
Revoke a member’s access to engines the same way you’d revoke any of their access — through your tenant’s member and role management, not per engine. Revoke a service user’s API key from Settings → Service users; any engine tokens it already holds stop being renewable, and a client-credentials token already issued expires on its own fixed schedule.Troubleshooting sign-in
Related
Connect to an engine
Every way a client reaches your engine, exactly as the Connect dialog offers them.
Roles and permissions matrix
What each role can do, including who can revoke a member’s access.