Documentation embedded in this build.
Documentation
Getting started
Run it, enrol, protect a service, ask for a mission — in an afternoon.
Scenarios
The ten shapes the box runs in, each with the command that stands it up and the smoke that proves it.
- Protect a service with an authorizing proxy
- A fleet of edge proxies around a central AuthBox
- Your own certificate authority for a team
- A federation across organisations
- Bring the organisation you already have
- Move labelled data only to the services cleared for it
- Hand out classified records only to the cleared
- A file that stays classified after it is copied
- SSH access to your hosts and your cluster's nodes
- A laptop with the cable out, or a cluster
- Give a service a certificate
User guide
For the person who holds a certificate.
- Enrolling with AuthBox
- The console, page by page
- How policy and missions fit together
- Glossary of resources
- How missions, obligations, and goals fit together
- Leaving the public CA
- Living with your certificate
- Revocation, and how to need it less
- Asking for access
- Signing
- Using authboxjs
- Claiming a credential from AuthboxVault
- Logging in to a machine
- Filing a file
- Can they? — asking before a door answers
- A day in the harbour watch
- The walkthrough, unattended
- Login with AuthBox
- The classification-routed upload
- Login with AuthBox, for an application that speaks SAML
- Who decides, and where AuthBox goes
- AuthBox next to a service mesh, an identity provider and an ingress controller
Reference
The design system
Every token, both themes and each component, rendered from the stylesheet the product's own pages are drawn with.