Skip to main content

Documentation Index

Fetch the complete documentation index at: https://stackauth-e0affa27-chore-move-mcp-to-a-sep-app.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Stack Auth supports a variety of authentication providers to give your users flexible sign-in options. You can configure these providers through the Stack Auth dashboard.

Overview

Authentication providers determine how users can sign in to your application. Stack supports the following provider types:
  • Email/Password: Traditional email and password authentication
  • Magic Link: Passwordless authentication via email links
  • OAuth Providers: Third-party sign-in with providers like Google, GitHub, Facebook, Microsoft, and more
  • Passkeys: WebAuthn-based passwordless authentication

Configuring Providers

1

Open the Stack Auth dashboard

Navigate to your project in the Stack Auth dashboard.
2

Go to Auth Providers

Click on the Auth Providers section in the sidebar.
3

Enable providers

Toggle the providers you want to enable for your application.
4

Configure OAuth providers

For OAuth providers, you can use Stack’s shared keys for development or configure your own OAuth client ID and client secret for production.

Shared vs. Custom OAuth Keys

For development and testing, Stack provides shared OAuth keys that work out of the box. For production, you should set up your own OAuth client credentials.

Shared Keys

Shared keys allow you to quickly get started without needing to register your application with each OAuth provider. These are suitable for development only.

Custom Keys

For production use, configure your own OAuth client ID and client secret for each provider:
  1. Register your application with the OAuth provider (e.g., Google Cloud Console, GitHub Developer Settings)
  2. Obtain the client ID and client secret
  3. Enter them in the Stack Auth dashboard under the respective provider settings

OAuth Providers

GitHub

Sign in with GitHub

Google

Sign in with Google

Facebook

Sign in with Facebook

Microsoft

Sign in with Microsoft

Spotify

Sign in with Spotify

Discord

Sign in with Discord

GitLab

Sign in with GitLab

Apple

Sign in with Apple

Bitbucket

Sign in with Bitbucket

LinkedIn

Sign in with LinkedIn

X (Twitter)

Sign in with X

Twitch

Sign in with Twitch

Other Authentication Methods

Passkey

WebAuthn-based passwordless authentication

Two-Factor Auth (2FA)

TOTP-based two-factor authentication

Going to Production

When preparing your application for production, make sure to:
  • Replace shared OAuth keys with your own client credentials
  • Configure a custom email server for email-based authentication
  • Set up proper redirect URLs for OAuth providers
For more details, see Going to Production.