Skip to content
AuthAction Documentation

AuthAction Documentation

Everything you need to add OAuth 2.0 and OpenID Connect authentication to an application: hosted login, passkeys, social and enterprise connections, machine-to-machine tokens, and MCP authorization for AI agents.

If you are starting from scratch, the three steps below take you from a new account to a working login.

Start here

Section titled “Start here”

  1. Create a tenant

    A tenant is your isolated identity environment, with its own users, connections and domain. You get one for development and one for production.

  2. Register an application

    Tell AuthAction what is connecting: a single-page app, a regular web app, a native app, or a machine-to-machine service. This is where your client ID and callback URLs live.

  3. Integrate your app

    Drop in the SDK for your framework, point it at your tenant domain and client ID, and you have a login.

New to the dashboard? Getting started walks through it screen by screen.

Integrate your application

Section titled “Integrate your application”
Frontend React, Angular, Vue, Next.js, Nuxt, Remix, SvelteKit and vanilla JavaScript.
Backend APIs Validate JWTs and protect endpoints in Express, NestJS, Spring, Go, .NET, Django, Flask, Rails, Rust, PHP, Laravel and Apollo GraphQL.

Add login methods

Section titled “Add login methods”
Social connections Google, GitHub, Microsoft, LinkedIn, Amazon and more.
Enterprise connections SAML SSO and LDAP: Okta, Azure AD, Google Workspace, ADFS, PingFederate, JumpCloud and Active Directory.
Passkey Plus WebAuthn passwordless sign-in alongside your existing login methods.
Database connections Username and password sign-in against AuthAction's own user store.

Go deeper

Section titled “Go deeper”
Authentication flows OAuth 2.0 endpoints, PKCE, passkeys, OIDC prompt parameters, native apps and token exchange.
Users, roles and organizations Manage users, assign roles and permissions, and invite people to a tenant.
Platform Multi-tenancy, regions, custom domains and how AuthAction URLs are structured.
Management API Automate users, roles and tenant resources with a machine-to-machine application.
MCP server Dynamic client registration and authorization for Model Context Protocol servers.
CLI Manage tenants, applications, users, roles and connections from the terminal.

Support

Section titled “Support”

Something missing or unclear in these docs? Email support@authaction.com.