Manual for Bouncer 0.5.7. Chapters state version and distribution limits. Source cdd3b59, site build 20 November 2026. Your server or app may run an earlier version.
On this page
Approvals and access duration
Bouncer keeps two clocks apart: the time an approver has to answer, and how long the access lasts.
The time to answer
When someone asks for access, the request waits for an approver for a limited time. The app shows it as "N left to answer" on the request and in the inbox. Your administrator sets how long requests wait. By default it's 15 minutes, and a server can set anything from 1 minute to 24 hours.
If nobody answers in time, the request expires and nothing is granted. The app says "This request expired" and that nothing was granted. The requester can ask again.
The time to answer says nothing about how long access lasts.
How long access lasts
When you approve, you choose how long the access lasts. The request shows Access for with the length the requester asked for (for example "Access for 1 hour", marked Requested), and on a phone the button says Approve 1 hour. To choose another length, tap Change. You get How long? with:
- the quick choices your server offers. By default these are 5m, 15m, 1h, 6h, 24h, 7d and Always (see Standing access). A choice the resource doesn't allow is shown greyed out with the reason, for example "Not allowed for prod-db-password. Its policy allows up to 24 hours.";
- Custom…, for any whole number of minutes, hours or days from 1 minute up to the resource's limit (at most 365 days).
If you pick a longer time than was asked for, the app asks you to confirm (Longer than requested), and the approval records that it's longer.
The access you approved is called a grant. It appears under Grants with its end time, and you can end it early there with Revoke.
Standing access ("Always")
Your server may offer Always, described in the app as "Standing, until you revoke it". It's in the default list unless your administrator turns it off. Always is experimental and may change or be removed, so choose a time limit instead. If you see standing grants, check them with your administrator.
What happens during a grant
For a stored secret or API key, Bouncer doesn't hand over the secret once and walk away. The requester gets short-lived tokens that can only read that one secret. Each token lasts a few minutes (5 minutes by default; the request says how long), and Bouncer issues new ones until the grant ends.
When the grant ends, or you revoke it:
- Bouncer stops issuing tokens and revokes the ones it already issued, so new reads stop.
- A value that has already been read can't be recalled. If the requester copied the secret somewhere, it still has it. If you think it was misused, change (rotate) the secret where it's used.
- Open sessions may continue. For example, a database connection opened with the secret may stay open until the database closes it.
The app says this in the request ("Anything already read can't be taken back, and open sessions may continue") and again when you revoke.
SSH access
For an SSH host, the requester gets a short-lived SSH certificate for one account, never a stored key. There is no value to view or copy. A certificate expires no later than the grant's end. If you revoke early, a host refuses certificates already issued only once it fetches Bouncer's updated revocation list. Until then, or until expiry, they can start new connections. In 0.5.6 and earlier, hosts can't fetch a new list while OpenBao is unavailable. From 0.5.7, Bouncer serves the list from its database during an OpenBao outage, once it has read the CA public key (issue #281; see SSH revocation). Bouncer does not cut off a connection already open.
Saving new values (store requests)
Some requests ask to save new values into a secret, rather than read it. The request says "wants to save new values to" the credential and lists the field names, never the values.
- Approving allows one update of those fields, sent within a short window shown on the request.
- The saved values stay after that window. The window only limits when they can be sent.
- Approving a save doesn't let anyone read the secret, and you never see the new values. They go straight to the secret store; Bouncer doesn't keep them.
Deny a save if you weren't expecting the change.
A short example
Alice's deploy script asks for prod-db-password for 1 hour, with the reason
"Nightly schema migration". The request waits up to 15 minutes. Bob, an
approver, opens it after 3 minutes, changes the duration to 15m because the
migration is short, and approves with his fingerprint.
- The request is answered: nothing more happens on the 15-minute answer clock.
- The grant runs for 15 minutes from Bob's approval. The script gets 5-minute tokens, renewed until the grant ends.
- After 15 minutes, new reads stop. If the script wrote the password to a log file, that copy still exists, so Bob would rotate the password.