Skip to content

Introduction

SeekAuth is a login service for your product. It is an OpenID Provider and an OAuth 2.1 authorization server: it holds your users’ accounts, shows them the login, and gives your app signed tokens that say who is logged in and what they may do. You configure it in the dashboard at auth.dev.seek.services or through the management API, and add it to your app with an SDK or any OpenID Connect library.

  • Logins. Email codes, passwords, passkeys, Google, Apple, GitHub, Discord, X and Microsoft, Solana and EVM wallets, and (on paid plans) any provider of your own that speaks OpenID Connect or OAuth 2. Each one is a switch. See Login methods.
  • On your page or on ours. The login opens in a dialog on your own page, in your colours and with your app’s name, or on a hosted page your app redirects to. Both are the same login. See How a login works.
  • Two-step login. Authenticator apps and passkeys, with recovery codes: optional, required for everyone, or asked for before a sensitive action. See Two-step login.
  • One account across your apps. Apps in one group share their users, and a user arrives signed in when moving between them. See Apps that share accounts.
  • Roles and permissions. You define your APIs and what may be done with them; access tokens carry the user’s roles and the permissions for the API they are for. See Roles and permissions.
  • Standard tokens. ES256 access tokens your backend verifies offline against the published keys, rotating refresh tokens, and DPoP so that a copied token is no use elsewhere. See Tokens and claims.
  • Machines too. Jobs and services get tokens of their own with client credentials. See Machine client.
  • The rest of a login. Sign-up rules and bot protection, sessions and how long they last, webhooks to your servers, an audit trail, custom domains, analytics.
You want to Read
Understand the parts Concepts, then How a login works
Add a login to a React app Quickstart: React SPA
Keep tokens on your server Quickstart: web backend
Check tokens in your API Quickstart: protect an API
Call an API from a job Quickstart: machine client
Use your own OpenID Connect library Discovery and keys, /authorize, /token
Automate the setup Management API
Know the limits Plans and limits

SeekAuth implements OpenID Connect discovery, the authorization code flow with PKCE (S256, required), refresh token rotation, client credentials, DPoP (RFC 9449), resource indicators (RFC 8707), token revocation (RFC 7009) and introspection (RFC 7662), the iss parameter in authorization responses (RFC 9207), and RP-initiated logout. It does not offer the implicit or hybrid flows, request objects, pushed authorization requests, the device flow, or front- and back-channel logout.