TokenLogin — Authentication tokens
Bearer tokens, API keys, OAuth-style secrets.
Token Login type (TokenLogin, discriminant 3) — Passwords category. Bearer tokens, API keys, OAuth-style secrets.
Classification
← Types index · Category: Passwords · Discriminant: 3
Field schema (EntryData)
| Field | Rust type | Optional | Protected | UI label |
|---|---|---|---|---|
client_id | Option<String> | yes | no | Client ID |
token | String, // Primary access token | no | yes | Token |
refresh_token | Option<String> | yes | yes | Refresh Token |
token_expiry | Option<String> | yes | no | Expiry date |
api_key | Option<String> | yes | yes | API Key |
bearer_token | Option<String> | yes | yes | Bearer Token |
url | Option<String> | yes | no | URL |
notes | Option<String> | yes | no | Notes |
Secrets
Protected fields (masked in UI, EntryType::is_protected_field): token, refresh_token, api_key, bearer_token.
Attachments
Attachments
Like all entry types, a TokenLogin entry may have encrypted attachments via Entry.attachments (EntryAttachments: files, folders). Add them by drag-and-drop in the entry editor; binary content is encrypted with the vault.
In the app
Create a Token Login entry: vault → + → type TokenLogin → fill fields → add attachments (optional, all types) → Save. Validation: only title is required (validation_service.rs).