# RabbitMQ temporary access

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

RabbitMQ targets create users through the management plugin's HTTPS API, with
permissions limited to one virtual host. Set each permission as a RabbitMQ
resource-name regular expression; all default to `^$` (no named resources).

```json
{"provider":"rabbitmq","executor":"in_do","endpoint":"https://rabbit.example.com:15671","vhost":"/","read":"^events\\.","write":"^jobs\\.","configure":"^$"}
```

Supply encrypted management JSON with `username` and `password` for an account
allowed to manage users and permissions. The endpoint is the management origin,
not the AMQP listener. Register and mint through the dashboard or `seekrit dynamic`.
Output contains `username`, `password`, and `vhost`; use your cluster's AMQP
address to connect. Generated users receive no management tags, and the broker
sends RabbitMQ's salted SHA-256 password hash rather than the plaintext password.

RabbitMQ users have no native TTL. The broker deletes the user on revocation
and expiry, retries failed deletion, and retains cleanup after failed permission
assignment. Keep the broker available for timely expiry.

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