Guides
Each guide says what a feature does, how to turn it on in the dashboard and with the management API, and the rules it follows.
| Page | What it covers |
|---|---|
| Login methods | The ways users can log in to a SeekAuth environment, how to turn each one on, and how email codes and passwords behave. |
| Two-step login | Second factors (authenticator apps, passkeys, recovery codes), requiring them for an environment or a role, and asking for a stronger or more recent login before a sensitive action. |
| Passkeys | The passkey domain, turning passkeys on, how users add them in account settings, and how they log in with one or use it as a second factor. |
| Social and custom providers | Logging in with Google, Apple, GitHub, Discord, X and Microsoft, or a provider of your own that speaks OpenID Connect or OAuth 2, and how their accounts link to existing ones. |
| Wallets | Logging in with a Solana wallet (Sign In With Solana) or an EVM wallet (Sign In With Ethereum), what is signed, and how wallet accounts work. |
| Sign-ups and access | Who may create an account in an environment, who may use each app, accepting an app’s terms, and apps that need every user to have an email address. |
| Bot protection | What keeps scripted sign-ups out - captchas, the rules on tagged, throwaway and Gmail-variant addresses, the daily cap on new accounts and the monthly pause - and what users see. |
| Roles and permissions | Define your APIs and their permissions, group permissions into roles, give roles to users and machine clients, and check them in your backend. |
| Calling your API | Get an access token for the right API, send it from a single-page app or a web backend, and verify it in your API with the Rust SDK or any JWT library. |
| DPoP | How SeekAuth binds a browser’s tokens to a key that never leaves it, what a DPoP proof must contain, and how an API checks one. |
| Sessions and sign-out | What a session is, how long it lasts, how each kind of app signs a user out, and how a user or an admin ends sessions everywhere. |
| Apps that share accounts | Put several apps in one group so they share their users and sessions, while each keeps its own name, look, rules, clients, APIs and roles; and carry a login from one app to another with a session ticket. |
| Account settings for your users | Give your users a settings page for their profile, password, email address, two-step login, passkeys, linked logins and sessions, with ready-made components or the account API. |
| Webhooks | Get told when users sign up, log in, change or are deleted - the events, the payload, verifying the signature, and how deliveries are retried. |
| Custom domains | Serve an environment’s login on a domain of your own, such as id.your-app.com - prove the domain with a DNS record, then move the issuer to it. |
| Branding | Give the login your app’s colours, corners, font, logo and words, for a whole environment or for one app, and know where your app’s name appears. |
| Going to production | What differs between an app’s development and production environments, and a checklist for setting production up before your users arrive. |