DOCSEARCHbyAlgolia
Submit Docs

Authdog Documentation

website·Indexed 33 days ago

https://www.authdog.com/docs

Identity management platform providing authentication, authorization, and session handling. Features include multi-tenancy, SCIM 2.0 provisioning, Lidar identity SIEM, and support for SAML 2.0, OpenID Connect, and Passkeys. Includes tools for machine-to-machine (M2M) identity, Model Context Protocol (MCP) server security, and official SDKs for Python and Zig.

Tokens
113K
Snippets
288
Records
890
Agent score
67%

What's inside Authdog

  1. Overview of Authdog Actions

    Actions are synchronous hooks that run during an authentication flow. Unlike webhooks, actions are awaited inline and can determine the outcome of the flow by allowing, denying, or enriching the session with custom token claims. They are used to enforce backend-owned rules (e.g., blocking disposable emails, requiring allow-lists, or injecting entitlements) without modifying hosted flows.

  2. Overview of Authdog Pipes for third-party integrations

    Authdog Pipes allows applications to connect end-users to third-party accounts (e.g., CRM, Google) by managing the OAuth2 consent flow. Authdog handles the storage of tokens (encrypted at rest) and automatic refreshing, allowing the backend to simply request a fresh access token for a specific user and provider without managing the refresh logic manually.

  3. Overview of Authdog Audit Logs

    Authdog audit logs record authentication and administrative activity for investigation, compliance, and operational monitoring. There are two primary types of logs:

    • Environment logs: Cover identity activity (e.g., sign-ins, MFA).
    • Organization logs: Cover organization-level changes (e.g., management activity).

  4. Overview of Authdog UI components

    Authdog provides a set of prebuilt, themeable UI components via the @authdog/react-elements library. These components allow developers to embed authentication surfaces (like user profiles and menus) directly into their own application layout, serving as a middle ground between using a hosted Account Portal and building fully custom headless flows.

  5. Overview of Authdog Connectors

    Connectors are external identity providers (such as Apple, Google, Meta, Microsoft, and GitHub) that users use to sign in. Authdog manages the OAuth 2.0 exchange, normalizes the returned profile, and links it to an Authdog user. This ensures the application only interacts with an Authdog session, while the provider's identity is stored as a linked identity on the user record. Connectors are configured per environment (Development, Staging, Production), meaning each environment has its own client credentials and callback URLs.

  6. Overview of Authdog email delivery providers

    Authdog environments deliver transactional authentication emails using either a managed provider (default) or a single connected custom provider. Only one provider can be active per environment. Configuration is environment-specific; you must configure development and production environments separately with their respective credentials and sender domains.

  7. Overview of Badge authentication

    Badge is an authentication provider that replaces stored credentials with a device-independent key derived during each authentication. This architecture ensures there is no secret at rest to steal, making it ideal for products designed to mitigate the risk of credential-database exposure.

  8. Overview of Authdog Lidar (Identity SIEM)

    Lidar is Authdog's identity SIEM used for threat detection, monitoring, and security intelligence. It is available on a per-environment basis and requires a selected project and environment to function. Lidar is a paid-plan feature available to Team, Pro, and Enterprise plans (feature slug lidar). It can be accessed via the sidebar at the /dashboard/security route.

  9. Overview of Authdog Bot Protection

    Authdog provides bot protection for hosted authentication flows to prevent automated sign-ups, credential stuffing, password-reset spam, and one-time-code abuse. It supports two providers: Google reCAPTCHA and Cloudflare Turnstile. Protection is configured per environment. If both providers are enabled for the same flow, Google reCAPTCHA takes precedence. Bot protection filters traffic before authentication and is intended to complement Lidar detections and rate limiting.

  10. Overview of the Audit module

    The Audit module serves as the searchable record of all activity within an environment. It provides summaries, searchable events, and type breakdowns. The module uses a global time range picker (reflected in the URL as &rt=..., e.g., &rt=24h) to filter data across all tabs. Users can apply and save filters in the top-right of every tab to narrow down investigations.

  11. Overview of Authdog Lidar

    Lidar is Authdog's identity SIEM designed to ingest, detect, and investigate authentication event streams. It monitors events for each environment, correlates related activity, and surfaces suspicious patterns as Signals in the console. While Lidar provides built-in identity investigation, event streams can also be forwarded to external SIEMs like Datadog, Splunk, or Sentinel via notification channels.

  12. Overview of the Agents environment registry

    The Agents registry (/dashboard/agents) is used to register, authorize, and audit AI agents and machine identities (such as OIDC client IDs, SPIFFE IDs, or URIs) that call your APIs and MCP servers.

    Key constraints:

    • Environment Scoped: Agents are registered per project and environment. An agent created in dev is not automatically registered in prod.
    • Access Control: This feature is sales-gated (feature slug agents). Users must request access via Support if the page shows a locked landing.