> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hexclave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# All Auth Providers

> Configure authentication providers for your application

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

## Overview

Authentication providers determine how users can sign in to your application. Hexclave 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
* **Custom OIDC**: Bring any OpenID Connect-compliant identity provider (Okta, Auth0, Keycloak, and others)
* **Passkeys**: WebAuthn-based passwordless authentication

## Configuring Providers

**1. Open the Hexclave dashboard**

Navigate to your project in the Hexclave 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 Hexclave's shared keys for development or configure your own OAuth client ID and client secret for production.

## Shared vs. Custom OAuth Keys

> [!NOTE]
>
> For development and testing, Hexclave provides shared OAuth keys that work out of the box. For production, you should set up your own OAuth client credentials. Custom OIDC providers always use your own credentials.

A [development environment](https://docs.hexclave.com/guides/going-further/local-vs-cloud-dashboard.md) typically uses shared keys. Configure your own client ID and secret in the [cloud dashboard](https://app.hexclave.com) before you launch.

### 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 Hexclave dashboard under the respective provider settings

## OAuth Providers

> [card] [GitHub](https://docs.hexclave.com/guides/apps/authentication/auth-providers/github.md)
>
> Sign in with GitHub

> [card] [Google](https://docs.hexclave.com/guides/apps/authentication/auth-providers/google.md)
>
> Sign in with Google

> [card] [Facebook](https://docs.hexclave.com/guides/apps/authentication/auth-providers/facebook.md)
>
> Sign in with Facebook

> [card] [Microsoft](https://docs.hexclave.com/guides/apps/authentication/auth-providers/microsoft.md)
>
> Sign in with Microsoft

> [card] [Spotify](https://docs.hexclave.com/guides/apps/authentication/auth-providers/spotify.md)
>
> Sign in with Spotify

> [card] [Discord](https://docs.hexclave.com/guides/apps/authentication/auth-providers/discord.md)
>
> Sign in with Discord

> [card] [GitLab](https://docs.hexclave.com/guides/apps/authentication/auth-providers/gitlab.md)
>
> Sign in with GitLab

> [card] [Apple](https://docs.hexclave.com/guides/apps/authentication/auth-providers/apple.md)
>
> Sign in with Apple

> [card] [Bitbucket](https://docs.hexclave.com/guides/apps/authentication/auth-providers/bitbucket.md)
>
> Sign in with Bitbucket

> [card] [LinkedIn](https://docs.hexclave.com/guides/apps/authentication/auth-providers/linkedin.md)
>
> Sign in with LinkedIn

> [card] [X (Twitter)](https://docs.hexclave.com/guides/apps/authentication/auth-providers/x-twitter.md)
>
> Sign in with X

> [card] [Twitch](https://docs.hexclave.com/guides/apps/authentication/auth-providers/twitch.md)
>
> Sign in with Twitch

## Other Authentication Methods

These aren't OAuth providers, but round out how users sign in and secure their accounts.

> [card] [Passkey](https://docs.hexclave.com/guides/apps/authentication/auth-providers/passkey.md)
>
> WebAuthn-based passwordless authentication

> [card] [Two-Factor Auth (2FA)](https://docs.hexclave.com/guides/apps/authentication/auth-providers/two-factor-auth.md)
>
> TOTP-based two-factor authentication

> [card] [Custom OIDC](https://docs.hexclave.com/guides/apps/authentication/auth-providers/custom-oidc.md)
>
> Bring any OpenID Connect identity provider (Okta, Auth0, Keycloak, and more). Team plan or above.

## 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](https://docs.hexclave.com/guides/apps/launch-checklist/overview.md).