Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

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

An approval and the access it grants are different things, and each has its own limits. The app-side explanation is in Approvals and access duration; this page adds what the server enforces.

Three times

TimeWhat it limitsDefaultSet by
Time to answer (request_wait)How long a request waits for a decision. After it, the request expires and nothing is granted15 minutes (1 minute to 24 hours)The config file
Access durationHow long the grant lasts, from the moment of approvalWhat the requester asked, unless the approver changes it (1 minute to 365 days)The requester asks; the approver decides, within the resource's policy
Token lifetime (credential_ttl)How long each OpenBao token lasts5 minutes (30 seconds to 1 hour), and never past the grant's endThe config file, capped by the role kit

The server's clock is the only one that counts. Expiry needs no background job: every check compares the current time with the grant's end, so a grant can't outlive its time because a job didn't run or the server restarted.

What an approval allows

During a grant, the requester can fetch as many fresh tokens as it likes, each lasting the token lifetime, and read the resource's secret with them. So a grant is permission to read the secret repeatedly until it ends, not a single read.

What the approver agreed to is fixed by the signature: this resource, this requester, this duration, this reason. If the resource's policy changes afterwards, a pending decision against the old policy is refused, and standing grants on it are suspended.

Ending access early

Access ends early when:

  • an approver revokes the grant in the app;
  • the requester revokes it itself (bouncer revoke, or the MCP revoke_grant tool);
  • the admin disables the requester, or pulls the kill switch;
  • the admin revokes the device that approved it, for standing grants only. Time-limited grants approved by a revoked device stay until they end, and the admin is shown a list so they can end them by other means.

A revoke stops new tokens at the moment it's committed, then revokes the tokens already issued. If OpenBao doesn't confirm a token's revoke, the server keeps retrying until it does or the token expires.

None of these can take back a value that was already read: see Copied secrets and revocation limits.

Standing grants ("Always")

The source supports standing grants, which have no end time. The Bouncer project hasn't decided the policy for standing grants yet. Keep them off. They are not an approved feature. If you run a server, turn them off with durations.always: false, and leave always out of the presets.

A related mode is also undecided: "Always approved" for personal credentials, where an owner lets their own credential be used without approving each time. It has two open problems: under Always approved, a person's command-line key gets the value with no device involved, and the kill switch doesn't stop Always approved uses. Keep it off: leave ceilings.always_approved: false (the default) on every personal-credential storage area.

When a server does allow standing grants, the source limits them in these ways:

  • each is suspended when its review is due (every 90 days by default), unless the admin re-confirms it;
  • each is suspended when its resource's policy changes, when its resource is removed, or when its requester gets a new key;
  • a suspended grant never becomes active again; the requester must ask again.

This manual covers Bouncer 0.5.7. Built from source commit cdd3b5958d5be0b33e865b1b56b770f6bccffaf7 (workspace version 0.5.7+34).