Tokens (including the long-lived refresh_token) are written in plaintext to
<cwd>/.token/ (or options.directory). Writes are atomic: the token is written to a
temporary file and renamed into place, so a crash never leaves a half-written token. The directory is restricted to mode 0700 and files to 0600,
and a .gitignore is written inside the directory so its contents are not
committed. For production deployments prefer a secrets manager or an
encrypted database via a custom TokenStorage implementation.
File-based token storage.
Tokens (including the long-lived refresh_token) are written in plaintext to
<cwd>/.token/(oroptions.directory). Writes are atomic: the token is written to a temporary file and renamed into place, so a crash never leaves a half-written token. The directory is restricted to mode 0700 and files to 0600, and a.gitignoreis written inside the directory so its contents are not committed. For production deployments prefer a secrets manager or an encrypted database via a customTokenStorageimplementation.