Verify to connect
in progressRequire an OS-native identity check before SQLly opens a connection that deserves extra care.
Require an OS-native identity check before SQLly will even open a connection. Set it on a client, a project, or an environment, and every connection filed beneath it is covered. The hierarchy does the repetitive part for you.
In progress: the setting is stored, edited, and exported today, but SQLly does not yet raise the Touch ID / Windows Hello prompt, so turning it on does not block connecting yet. Raising the native prompt at connect time is the remaining work. The rest of this page describes the setting as it exists and the design the prompt will follow.
Turning it on
- Open Tools › Connection Management….
- Choose Clients, Projects, or Environments, then select the one to protect.
- Under Safety Features, tick Require Touch ID to connect.
The label says Touch ID on every platform. The design calls for Windows Hello on Windows, as described in Identity gates. The switch is off by default.
The setting is also in exported connection files, under each
label's safety object, so a team can share the same policy:
{
"format": "sqlly-credentials",
"version": 1,
"clients": [
{ "name": "Acme Corp", "safety": { "require_touch_id_to_connect": true } }
],
"environments": [
{ "name": "Production", "safety": { "require_touch_id_to_connect": true } }
]
}
See Connection file format for the rest of the file.
One server, or a whole customer
The switch lives on clients, projects, and environments, not on individual connections. To gate a single server, file it under its own environment or project and switch the gate on there. To gate a customer's whole estate, switch it on for the client. Following the inheritance rule, a group can only add a gate. If any level a connection belongs to asks for one, the gate will apply to it.
-- client Acme Corp Require Touch ID to connect: on -- env Production Require Touch ID to connect: off acme-prod-01 → gated (from the client) acme-dev-01 → gated (from the client) other-prod → not gated
Where the pause lands
By design, the check happens before the driver dials: before a login attempt, before the schema cache warms, and before the explorer expands anything. A connection you cannot verify for is a connection that was never made, which keeps the server's own audit log clean of half-opened sessions. If no identity check is available, the gate is designed to fail closed. See fallback.
When to reach for it
- A shared or unattended machine. The gate is about the person, not the statement, it is the only guardrail that helps when someone else is at your keyboard.
- A saved production connection you rarely use. Connecting by accident from the explorer becomes impossible rather than merely unlikely.
- A customer's environment you are contractually careful with. One switch on the client covers every database filed beneath it.
Deliberately not the default. A gate on your local scratch database is friction with no payoff, and a prompt you dismiss thirty times a day stops being a security control.