User management
Sign in your own end users with OhAuthCat: hosted login, passwords, passkeys, email codes, social sign-in, MFA, sessions and organizations.
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.
What you get
Section titled “What you get”- Hosted login: sign-in, sign-up, password reset, invitation and account pages on
signin., in six languages, with your branding. The API behind them, token revocation, logout and discovery are on<your domain> login..<your domain> - Sign-in methods: passwords, passkeys, email codes and social sign-in with seven providers.
- Multi-factor authentication: authenticator apps (TOTP), passkeys and one-time recovery codes, with environment and organization policies. SMS is not offered: NIST SP 800-63B lists it as a restricted authenticator.
- Sessions and tokens: authorization code with PKCE, short-lived access tokens, rotating refresh tokens, listing and revocation.
- Organizations, memberships and invitations, with an organization switcher on the hosted pages.
- Roles and permissions in the tokens, bot protection on sign-in and sign-up, and connected apps when other applications need access on your users’ behalf.
How it fits together
Section titled “How it fits together”- Your app redirects the browser to the hosted login with a PKCE challenge (
code_challenge_method=S256is required). - The user signs in with any method the environment (and, when the app asks for one, the organization) allows.
- The browser returns to your exact registered redirect URI with a single-use code that lasts 60 seconds.
- Your app exchanges the code at
POST /for an ID token, an access token and a refresh token.user_management/ token
The management API under /v1/users, /v1/invites, / and /v1/user_management/… needs the users:read or users:write scope. See the Management API reference.
Settings
Section titled “Settings”PUT / 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.
Events
Section titled “Events”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.
Monthly active users
Section titled “Monthly active users”Each sign-in counts the user once per calendar month (UTC). GET / 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.