mirror of
https://github.com/stack-auth/stack.git
synced 2026-06-13 21:01:21 +08:00
3fa081f1e3
<!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md -->
79 lines
2.6 KiB
Plaintext
79 lines
2.6 KiB
Plaintext
---
|
|
title: Auth Providers
|
|
description: Configure authentication providers for your application
|
|
---
|
|
|
|
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
|
|
|
|
<Steps>
|
|
<Step title="Open the Stack Auth dashboard">
|
|
Navigate to your project in the Stack Auth dashboard.
|
|
</Step>
|
|
<Step title="Go to Auth Providers">
|
|
Click on the **Auth Providers** section in the sidebar.
|
|
</Step>
|
|
<Step title="Enable providers">
|
|
Toggle the providers you want to enable for your application.
|
|
</Step>
|
|
<Step title="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.
|
|
</Step>
|
|
</Steps>
|
|
|
|
## Shared vs. Custom OAuth Keys
|
|
|
|
<Info>
|
|
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.
|
|
</Info>
|
|
|
|
### 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
|
|
|
|
## Supported OAuth Providers
|
|
|
|
Stack Auth supports the following OAuth providers:
|
|
|
|
- Google
|
|
- GitHub
|
|
- Facebook
|
|
- Microsoft
|
|
- Apple
|
|
- Spotify
|
|
- LinkedIn
|
|
- GitLab
|
|
- Bitbucket
|
|
- Discord
|
|
- X (Twitter)
|
|
|
|
For detailed OAuth configuration, including managing access tokens and scopes, see [OAuth](./oauth).
|
|
|
|
## 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](../getting-started/production).
|