# Snowflake temporary access

[Temporary access overview](/docs/concepts/temporary-access) covers target setup, connection methods, and credential handling.

Snowflake targets create `SERVICE` users with a fresh RSA key pair, using the
SQL API. This supports key-pair authentication without legacy service-user
password sign-in.

```json
{"provider":"snowflake","executor":"in_do","account":"organization-account","adminRole":"USERADMIN","roles":["READER"],"warehouse":"ANALYTICS"}
```

Supply a management Programmatic Access Token as the encrypted credential. Its
role needs permission to create/drop users and grant the selected roles; its
network policy must permit the broker. Optional `networkPolicy` applies a named
policy to the issued user. Role, warehouse, and policy identifiers use unquoted
Snowflake naming conventions and are normalized to uppercase.

The dashboard and `seekrit dynamic lease` return the account, generated username,
PKCS#8 `privateKeyPem`, role, and warehouse. Use the private key with your
Snowflake driver's key-pair authenticator. The private key never enters SQL or
the lease ledger. The first configured role becomes the default role.

The broker drops the user on revoke and at the requested expiry. Snowflake's
`DAYS_TO_EXPIRY` is also set, rounded **up** to a whole day; timely sub-day expiry
therefore depends on broker cleanup. Existing sessions are not forcibly ended.
SQL execution is checked through completion, including asynchronous responses;
partial creation retains cleanup. Renew by creating another lease.

See the [CLI reference](/docs/reference/cli) and [API reference](/docs/reference/api) for commands and endpoints.
