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

See and end access

The Grants tab shows the access that is in force for the resources you're an approver for, and the history of every decision. You can end any active grant early.

Active grants

Open Grants, then Active. Each grant shows:

  • who has access to what, for example "deploy-bot → prod-db-password";
  • the action and the length approved, and when it ends ("Read · 1 hour, until 14:30"), with the time left;
  • who approved it, on which device, and whether in the app or from the notification;
  • when the last token was issued.

Grants with an end time are under Time-limited. Grants approved with Always are under Standing, with their review date. 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 (see Standing access).

A grant leaves Time-limited at its end. A standing grant whose review date passes without your administrator re-confirming it shows as "Suspended" from that moment, with no Revoke: it gives no more access, and the requester has to ask again. The app doesn't wait for the server to tell it.

Revoke a grant

  1. In Grants, Active, find the grant and tap Revoke.
  2. Revoke this grant? says who loses access to what, and how early.
  3. Tap Revoke to confirm.
  4. You should see "Revoked. deploy-bot no longer has access."

Bouncer stops issuing tokens at once and asks OpenBao to revoke the ones already issued, so new reads stop. If OpenBao cannot confirm a revoke, Bouncer retries until it succeeds or the token expires (5 minutes by default). For SSH access, a certificate already issued keeps working at a host until that host fetches Bouncer's updated revocation list or the certificate expires. 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). A value already read cannot be recalled. If you think it was misused, rotate it where it is used. Open sessions may continue.

Revoking doesn't need your approval key, so it works on any paired device, including a Windows PC without Windows Hello.

History

Grants, then History, lists every decision, newest first, with filters: All, Approved, Denied, Revoked and Expired. Entries read like:

  • "Approved by Bob on Bob's Pixel, in the app · 15 minutes (asked for 1 hour)"
  • "Denied as not recognised by Bob on Bob's Pixel, from the notification · asked for 1 hour"
  • "Revoked by Bob on Bob's Pixel after 6 min of 15 minutes"
  • "Expired unanswered after 15 minutes · nothing was granted"
  • "Viewed prod-db-password (you, Bob's Pixel)", for a value viewed in the app

An entry that names no person ("Revoked after 6 min of 15 minutes") was ended by the requester or by an administrator on the server.

The full approval log is on your organisation's server. The app shows the part that concerns you.

Your own requests

Your own requests aren't here. They're on the Requests tab; see Ask for access.

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