Skip to content

Glossary

aal1, aal2: The assurance of a login, in the acr claim: aal1 for one factor, aal2 for two (or a passkey). A machine client’s tokens say client.

Access mode: Who may use an app: open (anyone in the group), invite_only or closed (only the users it was granted).

Access token: A short-lived ES256 JWT (typ at+jwt) for one API, which that API verifies offline.

Account API: The API on every issuer host, at /account/v1, through which a signed-in user manages their own account. Its audience is account.

amr: How the user logged in, as a list: email, pwd, otp, recovery, passkey, wallet, social.

API: A server of yours that takes access tokens. It has an audience and permissions.

API key: A secret (sk_dev_… or sk_live_…) for calling the management API from scripts and CI, for one workspace and one kind of environment.

App: One product in a group. It owns its name, look, access mode, terms, clients, APIs and roles.

App group: A set of apps that share their users. It owns the two environments.

Audience: The identifier of an API, which access tokens for it carry in aud, such as orders-api.

auth_session: The value that names an embedded login attempt between its steps. It lasts 15 minutes.

Authorization code: What a completed login gives the client, to exchange at /token with the PKCE verifier. One use, 60 seconds.

Challenge: What the login asks for next (identify, email_code, mfa, …), in the embedded login’s answers.

Client: A piece of software that logs users in or gets tokens of its own: spa, web, native or machine. It has a client_id, and a secret if it is web or machine.

Client credentials: The OAuth grant a machine client uses to get a token for itself.

Custom domain: A domain of yours, such as id.your-app.com, that an environment can be served on instead of its platform host. It becomes the issuer.

Custom provider: A login provider of your own, OpenID Connect or OAuth 2, with an id custom-…. Pro and Scale.

Development environment: The environment of a group for building and testing: localhost is allowed, built-in providers have shared credentials, and its users are not counted against the plan.

DPoP: Demonstrating Proof of Possession (RFC 9449): a client proves with each request that it holds the key its tokens are bound to.

Embedded login: The login in a dialog on your own page, driven through /authorize-challenge.

Environment: Production or development, of one group: its users, sessions, login methods, security policy, signing keys and issuer.

Hosted page: The login served on the issuer host, reached through /authorize.

ID token: A JWT for the client with who the user is.

Issuer: An environment’s address, such as https://your-app.auth.dev.seek.services. Its iss claim, and the host of all its endpoints.

JWKS: The environment’s public signing keys, at /jwks.json.

Machine client: A client that acts as itself, with no user, using client credentials.

Management API: The API at api.auth.dev.seek.services for configuring workspaces, apps and environments.

Monthly active user: A distinct person who logged in or renewed a session in production during the calendar month.

Permission: Something that may be done with an API, such as orders:write. Tokens carry the permissions of their API only.

PKCE: Proof Key for Code Exchange: the client sends the hash of a secret with the login and the secret with the code. SeekAuth requires S256.

Production environment: The environment of a group that your users use, counted against the plan.

Recovery code: One of ten single-use codes that stand in for a second factor.

Refresh token: An opaque token that renews the others. It rotates on each use; one used twice ends its session.

Rejection: A refused login step, with a code such as invalid_code; the attempt goes on.

Resource: The parameter (RFC 8707) that names the API a token is for.

Role: A named set of permissions given to users and machine clients, belonging to one app or to the whole group. It can require two-step login.

Security policy: An environment’s rules for two-step login, captchas and which addresses may sign up.

Session: One login on one device. It ends when revoked, after the inactivity timeout, or at its maximum length.

Session ticket: A one-time, one-minute value that carries a login to another app of the same group.

Sign-up mode: Whether an environment makes new accounts: only open does; invite_only and closed do not.

Slug: The short name of a group or app, from which the issuer hosts follow: {slug}.auth.dev.seek.services and {slug}-dev.auth.dev.seek.services.

Step-up: Asking a signed-in user for a stronger (aal2) or more recent login before a sensitive action.

Webhook: A signed HTTP request to your server when something happens to a user.

Workspace: Your team’s account: members, a plan, API keys and app groups.