Version 1.0.0-rc.82
A pre-release build. It installs only on a node with a pre-release licence.
Metadata
Release notes
Stratum v1.0.0-rc.82
Release candidate. It continues the Stratum 1.0 preview and is recommended for evaluation and staging. Hold production rollouts for the stable v1.0.0 release.
This release brings accounts and access control: people sign in with their own account instead of sharing a key, you decide what each of them may do and where, and scripts get tokens narrowed to the job they do.
People sign in as themselves
- An account for each person, with their own password and an authenticator app. Administrators must set one up; the first sign-in walks them through it and shows ten recovery codes, once.
- Sign in through your identity provider (OpenID Connect) next to, or instead of, passwords. Someone signing in for the first time gets an account automatically, holding nothing until you give it something.
- Your password again before a sensitive change, so a session left open on a desk cannot be used to give someone more power.
- Changing or resetting a password signs that account out everywhere, on every server, at once. The session you changed it in carries on.
You decide who may do what, and where
- Roles given on a path. The whole system, one server, one customer, or one machine. Someone can manage one customer's machines and see nothing else.
- Eleven built-in roles and your own, built from 36 individual permissions.
- Groups, so a role is given to several people at once.
- Take something away below a path you granted, without unpicking the grant.
- Permissions pages under Datacenter, and a Permissions tab on each machine, network and customer.
- Buttons follow your permissions. A control you may not use is shown disabled, with the reason, instead of failing when you press it.
- Your account page shows every permission you hold and how you came to hold it.
Tokens for scripts
- Personal API tokens, each narrowed to exactly what its script needs, and never more than the account it belongs to.
- Your existing operator API keys keep working exactly as before. They are listed alongside the new tokens, and you can narrow one — the key your billing system uses, say — to just the calls it makes.
- A token stops the moment it is revoked, its expiry passes, or its account is disabled, expires or is deleted. A token never creates a token that outlives it.
Across a cluster
- One set of accounts for every server. A change made anywhere reaches every server within seconds.
- A customer's keys and the tenant portal now work from any server, not only the one holding their machines. A machine on another server is reached, acted on, and its console opened, from whichever server you are signed in to.
- Each server checks every caller against its own copy, so a server cannot be told by another that someone may do something.
- A server cut off from the rest keeps working with the accounts it last knew and says so, in the console and in its audit records.
- Revoking access takes effect everywhere within seconds, and ends what it opened — open machine consoles included.
- Joining a cluster with accounts that clash is refused and says which clash, so nothing is overwritten by surprise. You can choose to join without the server's own accounts.
Refusals tell you nothing you should not know
- Something you may not see answers exactly as something that does not exist. A "not found" may simply mean it is not yours.
- Where you can see an object but lack the permission, the refusal names the permission and the path, so you know what to ask for.
Security review
This release includes an independent security review of the new access control, and the fixes for every issue it raised. Among them:
- Permission to manage accounts no longer carries the ability to take an account over. Handing an account to someone — through a token, a password reset, a second-factor reset, or re-enabling it — now requires holding what that account holds.
- A customer-scoped permission to manage networks can no longer create a network over another customer's addresses.
- Changing a customer's bandwidth cap requires the same permission as the billing calls that set it.
- To give someone a permission, you must be able to see them.
- A single customer can no longer use up every console ticket on a server.
Fixes
- Machine consoles. A console closing now always says why, and the reason no longer depends on timing.
- Peering. Two servers that end up sharing a peering identity now say so plainly instead of retrying indefinitely, and a working peering is no longer reported as down.
- Cluster audit. A cluster's audit log no longer reports healthy servers as unreachable to someone who may not read it.
- Sign-in limits count a whole IPv6 network as one address, and a burst of codes can no longer get past the per-account wait.
New in the API and command line
cenvero-str-ctl user | group | role | acl | token | realmmanage accounts, groups, roles, permissions, tokens and sign-in methods./api/v1/access/…covers the same ground, plusGET /api/v1/access/meand/access/permissionsfor what the signed-in caller may do.GET /api/v1/clusterand/cluster/statusreport whether access control is in use and ready.cenvero-str-ctl cluster join --discard-local-identityjoins without the server's own accounts.
Upgrade notes
- Nothing to do for existing keys. Every operator API key authenticates exactly as before, and the
apikeyscommands keep working. - Make your first administrator with
cenvero-str-ctl user add <name>@local --role Administrator --password-stdin. It sets up an authenticator app at its first sign-in. The installer prints this too. - On a cluster, every server must run this version before accounts are shared. Until then each server keeps its own accounts and the access API answers that it is not available yet, naming how many servers still need the update.
- If you link to the console from your identity provider's portal, link to the console itself (
https://<server address>:7070/console/), not to the address a sign-in starts at. - Root on a server's command line is always an administrator, so you can never lock yourself out of a server you can reach.
Feedback on this release candidate is welcome. Report issues through your account before the stable v1.0.0 cut.
Install
This is a pre-release (rc) build. It runs only on a node with a pre-release licence — the installer reads the channel from your licence, so a node on this key only ever pulls beta/rc updates, and a stable licence cannot install it. Run it once your pre-release licence is active:
printf 'X-License-Key: %s\n' "$KEY" \
| curl -sSL -H @- https://stratum.cenvero.com/install?channel=rc | sudo bash
// Set KEY to your licence key first. Passed this way, the key stays out of the server's process list.
// the ?channel=rc pin keeps this node on the rc channel for every later self-update — it never crosses beta↔rc.
Files
agent
| Architecture | File | Size |
|---|---|---|
| amd64 | cenvero-stratum sha256 1d378ecadbec388ce96a0d895011e41bf79592eb1586edd4140d2d18ed6a5d5b | 98.46 MB |
| arm64 | cenvero-stratum sha256 6952123e5d1364b497ce474ceae72f2f07f36c3ec529059cc19320860dfec89f | 86.81 MB |
ctl
| Architecture | File | Size |
|---|---|---|
| amd64 | cenvero-stratum sha256 451634c6b821630fcf34f9a072bc4ea612446267f2bc87d148b908f76103a5d3 | 29.45 MB |
| arm64 | cenvero-stratum sha256 97b6cc27aaae79f30b20e31b129f9ebbf93f838a97510f28d6619473da0d2d03 | 26.5 MB |
plugin-packer
| Architecture | File | Size |
|---|---|---|
| amd64 | cenvero-stratum sha256 6187ae92ef0ea2037ef36f4f8fccae957c34b3588beb89a10f02e72f9920be8b | 10.66 MB |
| arm64 | cenvero-stratum sha256 7f5da400740475017307a14b33c1cc9def7a53867dcbfe04eb25a9da6259cdb0 | 9.5 MB |
| darwin-amd64 | cenvero-stratum sha256 052027275da9e6801343a015ba35dace61058c6380847ad82df0882a0ae5cf46 | 10.48 MB |
| darwin-arm64 | cenvero-stratum sha256 356e3f54ad417edad9bd1608629dbe4050af99fcfeddf33696f4cc28cbc46279 | 9.36 MB |