Skip to content

FAQ

Do my users have to leave my site to log in?

Section titled “Do my users have to leave my site to log in?”

No. The login opens in a dialog on your own page, in your app’s look and with its name. A hosted page to redirect to is there as well, for apps that prefer it or cannot embed anything; both are the same login. Social providers always go through a redirect. See How a login works.

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. Codes by SMS are not available. See Login methods.

No. SeekAuth is a standard OpenID Provider: any OpenID Connect library works with the authorization code flow, PKCE (S256) and the discovery document, and any JWT library verifies the access tokens. The SDKs add the login on your own page, DPoP in the browser, and ready settings components.

The JavaScript SDKs are on npm: npm install @seek-services/auth-react, or @seek-services/auth-js without React. The Rust crate auth-client is not on crates.io: add it from the SeekAuth repository, by path from a checkout or as a git dependency. See Installing.

Verify a token. Access tokens are ES256 JWTs with your API as the audience and the user’s roles and permissions inside, checked offline against the environment’s published keys. The Rust crate does it in one extractor. See Protect an API.

Yes. Apps in one group share their users: someone who signs up in one can use the others with the same account, and can arrive signed in when moving between them. Each app keeps its own name, look, terms and rule for who may enter. See Apps that share accounts.

Yes: authenticator apps and passkeys, with recovery codes. Leave it to your users, require it for everyone, give a role that counts only after two steps, or ask for it before a sensitive action. See Two-step login.

As long as you say. Out of the box an access token lasts five minutes and is renewed without the user noticing, a login ends when nobody used it for 30 days, and after 90 days in any case. Each of these is a setting of the environment. See Lifetimes.

Yes. In Users or with the management API, end every session of a user; in Sessions, end one, or every session of the environment. Users can end their other sessions themselves in account settings (with a fresh login), and a change of password or email address, or turning on two-step login, ends them. An access token already issued works until it expires (minutes). See Sessions and sign-out.

Yes, at once and for good, from your app’s settings page: <DeleteAccount /> of auth-react, or the account API. It asks for a recent login and for the address to be typed. You can also delete a user on Users. Your servers are told with the user.deleted webhook. See Data and retention for what goes and what stays.

How do I delete my developer account or a workspace?

Section titled “How do I delete my developer account or a workspace?”

Your account: the account menu, then Account, then Delete my account. A workspace you are the only owner of has to get another owner, or be deleted, first. A workspace: its Settings page, then Delete workspace, which owners have; it takes every app, environment and user in it, and stops its subscription. See Delete a workspace.

No. There is no import or migration endpoint: users create their own accounts, and the management API does not create users or set addresses or passwords.

A distinct person who logged in, or whose session was renewed, in a production environment during the calendar month. Someone active in two apps that share accounts counts once. Development environments are not counted. See Plans and limits.

What happens when I reach my plan’s number of users?

Section titled “What happens when I reach my plan’s number of users?”

Logins never stop. On Free, new sign-ups pause until the month ends or you move to a larger plan. On paid plans you get an email at 80% and 100%, and new sign-ups pause only at half as many again: 15,000 on Pro, 150,000 on Scale.

Every sign-up with an email code or a wallet solves a captcha, addresses at throwaway email services are refused unless you allow them, and an environment takes at most 100 new accounts a day (20 in development). See Bot protection.

On Pro and Scale, yes. You prove the domain is yours with a DNS record, and the environment’s login address moves to it, such as id.your-app.com. That changes the issuer for every client. See Custom domains.

How do my servers learn that something happened?

Section titled “How do my servers learn that something happened?”

Webhooks: sign-ups, logins, changes to a user, ended sessions and more are sent to your endpoints, signed, and tried again for hours if your server is down. See Webhooks.

Yes. The management API does everything the dashboard does, with workspace API keys for scripts and CI.

What is the difference between development and production?

Section titled “What is the difference between development and production?”

Each app has both, with separate users, keys and settings. Development accepts http://localhost without registering it, lets the built-in social providers run on shared credentials, and is free on every plan. See Going to production.

Paid plans are a monthly subscription through LinkPay, started from the Billing page by an owner. Cancel there at any time: the plan stays until the end of the month you paid for, then the workspace returns to Free with nothing deleted.