Admin client certificates as an alternative to the admin token
rollcall admin-cert request NAME makes a key locally and sends a CSR; the region signs admin:NAME (client auth) and records the serial; a verified, recorded, unrevoked certificate is an admin. CLI/console read it from client.json, a .p12 is written for the browser; the web UI no longer insists on a token. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
28a0c2952f
commit
53c05bb44d
14 files changed
+492
-12
No files matched your search
@@ -430,6 +430,14 @@ plane is: `ca_dir` (default `/etc/rollcall/ca`) holds `ca.pem` and
|
||||
another architecture get `rack_binaries/rollcall-linux-<arch>`;
|
||||
`"auto_update": false` in `rack.json` opts out. `rollcall controllers`
|
||||
shows each rack's version.
|
||||
* **Admin certificates.** Instead of the admin token, a person or laptop can
|
||||
hold a client certificate: `rollcall admin-cert request NAME` (with the
|
||||
token once) makes a key locally, sends only a CSR and gets
|
||||
`admin:NAME` back; the CLI and console use it from `client.json`, and the
|
||||
`.p12` it writes goes into the browser's keychain, after which the web UI
|
||||
signs in by itself. `rollcall admin-cert list | revoke NAME` (revocation
|
||||
takes effect within 30 seconds). Certificates are checked against the CA,
|
||||
the client-auth usage and the serials the region recorded.
|
||||
* **Clients.** On the region host the CLI reads the CA from `ca_dir`;
|
||||
elsewhere `ROLLCALL_CA=ca.pem`, or the console shows the CA fingerprint on
|
||||
first connect and keeps the CA in `~/.config/rollcall/client.json` once you
|
||||
|
||||
Reference in new issue
Block a user