Identity and access

Who can do what in your projects.

People sign in with an email and a password, and can add a second step if they want one. After that, nobody can do anything until a role binding says so. Automation gets its own accounts and tokens, and every create, update, delete and refused request goes into an audit log.

Signing in

Sign-in, sign-up and single sign-on for the console happen at a sign-in service that is separate from the API. It has its own store and its own keys, and the API only ever reads its public keys. We split them on purpose: if one of the two is compromised, the other one's data is not exposed with it.

What we gave up is the API knowing anyone's email. It knows a person as an opaque subject. So there is no directory to search, and you can't invite someone by email. To the platform an email is a sign-in name and nothing more. We send no confirmation message, and no access decision ever looks at an email.

Passwords are 10 to 128 characters. There is no password reset, so keep yours somewhere safe. Sign-in attempts are rate-limited per address and per email, and after repeated failures the email is locked for 15 minutes. The responses never tell you whether an email exists.

Access tokens

A successful sign-in gives you an access token that lasts 1 hour. There is no refresh token. While your sign-in session is alive it renews the token by redirect. The API checks a token against the sign-in service's public keys and nothing else, so there is no revocation list. If an access token leaks, it stays valid until its hour runs out.

Two-step verification

You can turn on a second step for your own account. It uses TOTP: 6-digit codes every 30 seconds from any authenticator app, plus 10 single-use recovery codes. You set it up on the account page after signing in, and it is not offered through the API or the CLI. It is optional per person and cannot be required. Turning it on or off ends your other sessions.

Roles and bindings

Access is denied unless a binding allows it. A RoleBinding gives a Role to people, groups or service accounts, either on a project or on a billing account. There are built-in roles such as owner, editor, viewer and billing-admin, and you can write your own, up to 100 roles and 500 bindings per project.

kubectl get rolebindings
Where the binding livesWhat it covers
On a billing accountThe account and every project that belongs to it.
In a projectThat project only.

A role or binding never grants more than the person who wrote it holds, and the last owner of a billing account cannot be removed. The members view in the console lists who has access. To ask whether some other principal may do something in a project, use a SubjectAccessReview. The caller needs the verb on subjectaccessreviews in that project.

Service accounts and tokens

Give a script or a pipeline a service account instead of someone's login. It is an identity of its own, with its own API tokens.

kubectl get serviceaccounts
kubectl get apitokens

We show a token once and store only a hash of it, so it cannot be read back from the platform. If you lose one, create a new token and delete the old one. A token has all the rights of its owner. API tokens expire after 90 days by default and after 365 days at most. If you delete a service account its tokens stop working, and creating a new service account with the same name does not bring them back.

People get personal tokens too, up to 20 each. etorm login creates one for 30 days unless you ask for something else. It needs a browser on the same machine, because there is no device-code flow. The CLI is built from source.

Inviting people

To bring someone into a project you make an invitation for a chosen role and send them its link. Like a token, the link is shown once and stored only as a hash. An invitation never grants more than the person who made it holds.

kubectl get invitations

Each invitation has one link. By default it works once, but you can allow 1 to 50 uses. It is valid for 7 days unless you choose otherwise, 30 days at most, and a project can have at most 20 invitations.

The audit log

Each project keeps a log of who created, changed or deleted what, and who was refused. Request bodies and secrets are never recorded. Reads are not logged either. Owners and iam-admin can read it.

It holds the last 5000 changes and the last 1000 refusals per project, and nothing older than 90 days. There is no export, and the log does not record which token was used. There is one gap to know about. If the control plane fails between a change and its audit record, that one record can be lost. The change itself is kept.

The numbers in one place

WhatLimit
Passwords10 to 128 characters. No password reset.
Failed sign-insRate-limited per address and per email. Repeated failures lock the email for 15 minutes.
Access tokens from sign-in1 hour. No refresh tokens, no revocation list.
Two-step verificationOptional per person, cannot be required. Set up on the account page only.
API tokens90 days by default, 365 days at most. Shown once. 20 personal tokens per person.
etorm loginA token for 30 days by default. Needs a browser on the same machine.
InvitationsOne link each, 1 to 50 uses (default 1), valid 7 days by default and 30 at most, 20 per project.
Audit logThe last 5000 changes and 1000 refusals per project, kept 90 days. Reads are not logged. No export.
Quotas per tenant5 billing accounts per user, 100 access bindings per billing account, and per project 100 service accounts, 100 roles, 500 role bindings and 500 API tokens.
AccountsA sign-in account cannot be deleted, and its data cannot be exported.

Setting it up

If you want accounts for your team, write down who they are and what they need to reach, and ask us.

Request access