Expand description
OAuth2 authentication: PKCE loopback flow (RFC 8252) with an RFC 8628 device-flow fallback, tokens in the OS keyring.
Multi-account: one OAuth client, one token per Google account. An auth handle is bound to one account’s store entry (the default account keeps the legacy naming byte-for-byte); named accounts log in independently.
Structs§
- Auth
Config Builder - Device
Auth Challenge - Pending device authorization: show
verification_url+user_codeto the user, then poll withsuper::GoogleAuth::poll_device_codeuntil done. - Google
Auth - OAuth2 client with PKCE support
- Token
Storage - Token storage with automatic refresh.
Constants§
- SCOPES
- Union of every service’s scopes (Gmail, Calendar, Drive, People, Chat, Forms). Least-privilege selection is deliberately not implemented: one credential, everything works, nothing to configure.