Supported authentication providers
Use the providers index to compare supported identity systems, locate the correct adapter package, and jump into provider-specific documentation with a consistent structure.
Provider grid
Each provider guide covers overview, prerequisites, installation, configuration, authentication flow, example implementation, error handling, advanced configuration, best practices, and troubleshooting.
Integrate Firebase Authentication through the shared Aortem auth contract.
aortem_auth_firebaseOpen docsConnect Azure tenant policies and OpenID scopes with the same SDK surface.
aortem_auth_entra_idOpen docsBridge Cognito user pools and hosted UI flows into a single SDK contract.
aortem_auth_cognitoOpen docsDeploy Auth0 login, MFA, and custom domains through consistent SDK primitives.
aortem_auth_auth0Open docsMap Okta org configuration, policies, and logout handling to Aortem auth APIs.
aortem_auth_oktaOpen docsSupport passwordless email and wallet logins using Aortem session management.
aortem_auth_magicOpen docsUse Stytch factors, OTP, and passkey flows through the same auth abstractions.
aortem_auth_stytchOpen docsBring Ping authorization servers and enterprise login policies into a single SDK flow.
aortem_auth_pingOpen docsConnect Transmit CIAM login journeys and custom challenges to unified auth methods.
aortem_auth_transmitOpen docsUse device signals and risk scoring alongside Aortem session and policy controls.
aortem_auth_fingerprintOpen docsSelection guide
Enterprise deployments
Start with Entra ID, Okta, or Ping when tenant policy control and centralized workforce identity drive the rollout.
Developer-first teams
Auth0, Firebase, and Cognito fit teams that want hosted identity features with familiar cloud tooling.
Modern auth journeys
Magic, Stytch, Transmit, and Fingerprint help when passwordless, CIAM, device intelligence, or risk signals shape the integration.