enumeray auth refresh

Renew the selected profile’s browser login with its saved refresh token.

Use when: Explicit renewal is needed, including one-time migration of an already-expired legacy browser profile. Active commands normally renew saved browser sessions automatically.

Role and prerequisites: Any logged-in account. Install enumeray, configure the API and log in. Use an account or delegated token with the required permissions. Example IDs must be replaced with IDs from your service.

Example

enumeray --profile research auth refresh

Every command also accepts the profile, API, JSON and timeout options.

Result and next step

Saves replacement access/refresh tokens before verifying the original account. The original API and provider must match; a token-stdin login has no provider refresh token. An expired, revoked or uncertain refresh exchange requires another login.

Retry the desired command; if no refresh token exists, run auth login again.

Exact syntax, defaults and accepted values

Renew the selected browser login using its saved refresh token

Usage: enumeray auth refresh [OPTIONS]

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --profile <PROFILE>  Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>    Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --json               Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>  User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help               Print help