# Tailscale temporary access

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

Tailscale targets issue auth keys (`auth`), OAuth clients (`client`), or federated
identity trusts (`federated`). Register the target through the dashboard or
`seekrit dynamic target add`. A minimal auth-key configuration is:

```json
{"provider":"tailscale","executor":"in_do","tailnet":"example.com","credentialType":"auth","tags":["tag:ci"],"maxTtlSeconds":3600}
```

Supply an API access token as the management credential, or JSON with `clientId`
and `clientSecret` for an OAuth management client. That identity needs permission
to create, list, inspect, and delete the selected key type, and to assign the
configured tags/scopes. Keep management credentials in the encrypted credential
field or stdin; target configuration is public metadata.

Auth keys default to single use, ephemeral devices, and no preauthorization.
`reusable`, `ephemeral`, and `preauthorized` are optional booleans. OAuth and
federation targets require a nonempty `scopes` array. Federation also requires
an HTTPS `issuer`, `audience`, and `subject`. These permissions are fixed by the
target, rather than supplied by the lease requester.

`seekrit dynamic lease TARGET --ttl 30m` returns an auth key, an OAuth client ID
and secret, or a federation client ID. The broker deletes the issued key or
trust on revocation and at expiry, retrying failed deletion. Auth keys also have
upstream expiry; OAuth clients and federation trusts depend on broker cleanup.
Revoking an auth key does **not** remove devices already enrolled with it, and
revoking an OAuth client or trust does not promise to invalidate access tokens
already exchanged. Manage device removal and token lifetimes separately.

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