How Settings keeps secrets
Settings follows the model Grafana uses for data source secrets.
AvailabilityAvailable to everyone with early access to Varqeni.
Steps
- Write-only: a secret is sent once over HTTPS and then shows only as configured. No page, answer, log or history ever contains it. Reset removes it.
- Encrypted at rest: with AES-GCM under a 256-bit key the install creates on the Varqeni host and nobody types or sees. Each secret is bound to its own connection and field, so it cannot be moved to another.
- Your install wins: a secret your install placed (in its vault) is never replaced by one typed here.
- Every change is recorded: who changed what and which fields, in a hash-chained record. Secrets appear there only as changed, never as values.
What you should see: If the key on the host is lost, secrets added in Settings must be typed again; anything your install placed is untouched.
What it can and cannot do
Can
- Keep passwords and tokens encrypted on the Varqeni host, show them only as configured, and record every change without the value.
Cannot
- Show a saved secret again, or replace a secret your install placed.
Related articles
- Settings: connectionsEvery data source and integration Varqeni uses, in one place: what it is, where it points, whether it works, and a Test button.
- Settings history and rollbackEvery change in Settings is a new version: see who changed what, compare two versions, and roll back with one click.
- What Varqeni reads, and what it does notVarqeni reads the state of your pipeline, never the rows of your data.
Still stuck? Contact support or email info@fortisdatagroup.com.