# Milvus temporary access

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

Milvus targets use the v2 REST user-management API, with authentication enabled
and an HTTPS endpoint reachable from the broker.

```json
{"provider":"milvus","executor":"in_do","endpoint":"https://milvus.example.com","roles":["reader"]}
```

Supply `username:password` as the encrypted management credential, for an identity
permitted to create, list, grant roles to, and drop users. Pre-create the selected
roles with the desired database/collection permissions. Register and lease in
the dashboard or with `seekrit dynamic`; output contains `endpoint`, `username`,
and `password`. Usernames are generated from the lease identifier using a
collision-free encoding of characters Milvus disallows.

Milvus has no native user TTL. The broker drops the user at expiry or on revoke,
and retains cleanup after partial creation or failed deletion. Provider error
codes are checked even when HTTP returns 200. Existing sessions may remain usable
until Milvus refreshes authorization state; the broker does not terminate queries.

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