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
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.
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:- Register your application with the OAuth provider (e.g., Google Cloud Console, GitHub Developer Settings)
- Obtain the client ID and client secret
- Enter them in the Hexclave dashboard under the respective provider settings
OAuth Providers
GitHub
Sign in with GitHub
Sign in with Google
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
Sign in with LinkedIn
X (Twitter)
Sign in with X
Twitch
Sign in with Twitch
Other Authentication Methods
These aren’t OAuth providers, but round out how users sign in and secure their accounts.Passkey
WebAuthn-based passwordless authentication
Two-Factor Auth (2FA)
TOTP-based two-factor authentication
Custom OIDC
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