Secrets & vaults
Restura gives you three places to keep a credential so it never lands in a collection file, an export, or the UI’s state. All of them are desktop only — the browser has no OS keychain, so on web a secret is an inline value in IndexedDB. See Security for the threat model and ADR 0007 for the handle pattern.
OS-keychain handles
Section titled “OS-keychain handles”Auth fields (Bearer tokens, passwords, API keys, OAuth secrets) have a button next to the input to store the value in the OS keychain and reference it by handle. The field then holds only an opaque handle and a label. The desktop main process resolves the handle when the request is sent, and the plaintext never goes back to the UI. Manage stored handles under Settings → Secrets; a request whose handle is gone fails rather than being sent without credentials.
External cloud secret providers
Section titled “External cloud secret providers”Instead of copying a secret into Restura, a field can reference a secret that lives in a cloud secret manager. Supported providers:
- AWS Secrets Manager
- Google Secret Manager
- Azure Key Vault
Set up a profile. Open Settings → Secrets → External cloud profiles, choose a provider and add a profile. A profile holds identity locations only — for example an AWS region and named profile (or a workload-identity role ARN and token file), a Google project and credential-configuration file, or an Azure vault name and subscription. Provider credentials stay with the provider’s own SDK credential source (your AWS/Azure/Google login) and are never stored by Restura. Profile metadata is encrypted locally.
Reference a secret. On an auth field, choose the cloud-provider reference button, pick a profile, and enter the secret name (plus an optional version / stage and display label). The field stores the reference, not the value. The main process fetches the value when the request is sent, and resolved values never enter the renderer.
If a reference can’t be resolved — not found, access denied, or the provider isn’t reachable — the request fails with a message naming the provider and the reference’s display label (the provider’s raw error text is never shown); it is not sent unauthenticated.
In the CLI. The CLI has no profile store. Pass profiles with --external-secrets-config <file> (YAML or JSON); without it, a request that uses an external reference errors instead of being sent unauthenticated. See the CLI reference.
rs.vault in scripts
Section titled “rs.vault in scripts”Scripts can read and write the same kind of keychain-backed store:
// test script, after a login call: keep the new token out of variables and exportsawait rs.vault.set('ci-token', rs.response.json().token);
// any later script can read it back (resolves to undefined if the key is unset)const token = await rs.vault.get('ci-token');rs.test('token stored', () => rs.expect(token).to.be.a('string'));
await rs.vault.unset('old-token');rs.vault (and its pm.vault alias) has get(key), set(key, value) and unset(key), all async. Values live in the encrypted desktop store, not in environment variables, so they don’t appear in collection exports. The vault is not available on web, self-hosted or in the CLI; there the calls reject. See Scripts.
Related
Section titled “Related”- Authentication
- Environments — mark a variable secret to mask it.
- Import & export — handles never export as plaintext.