Skip to content
Dashboard
Theme
Theme

User management

Sign in your own end users with OhAuthCat: hosted login, passwords, passkeys, email codes, social sign-in, MFA, sessions and organizations.

View Markdown

User management makes OhAuthCat the whole sign-in system for your application’s own users, next to the enterprise SSO and directory sync your customers configure. Everything is scoped to one environment: the same email address in two environments is two unrelated users, and a token from one environment is never accepted by another.

  1. Your app redirects the browser to the hosted login with a PKCE challenge (code_challenge_method=S256 is required).
  2. The user signs in with any method the environment (and, when the app asks for one, the organization) allows.
  3. The browser returns to your exact registered redirect URI with a single-use code that lasts 60 seconds.
  4. Your app exchanges the code at POST /user_management/token for an ID token, an access token and a refresh token.

The management API under /v1/users, /v1/invites, /v1/organizations/{org}/memberships and /v1/user_management/… needs the users:read or users:write scope. See the Management API reference.

PUT /v1/user_management/settings sets the environment’s sign-in methods, require_name (ask for a name at sign-up) and native_app_origins (apps allowed to run passkey ceremonies). A method turned off for the environment, or for the organization the flow signs into, answers login_method_disabled.

User management emits user.created, user.updated, user.deleted, user.invited, membership.created, membership.updated, membership.deleted, session.created and session.revoked, plus user.sign_in.challenged and user.sign_in.blocked from bot protection. See the webhook event catalogue.

Each sign-in counts the user once per calendar month (UTC). GET /v1/user_management/usage returns the current month’s count and your plan’s limit. Plan limits for user management are not final; the pricing page is the source for them.