DashboardAuthentication
Auth Providers
Configure identity-based authentication using Supabase, Firebase, Auth0, or Clerk
Auth providers let your users authenticate to MQTT using their existing application credentials. No separate MQTT passwords needed.
How It Works
- Your user signs in to your app via your identity provider
- Your backend requests a temporary MQTT token from CloudSignal's token exchange API
- The device connects to MQTT using the token as credentials
- CloudSignal validates the token and allows the connection
Supported Providers
| Provider | Status | Setup Guide |
|---|---|---|
| Supabase | Supported | Guide |
| Firebase | Supported | Guide |
| Auth0 | Supported | Guide |
| Clerk | Supported | Guide |
Configuring a Provider
- Navigate to Dashboard → Authentication
- Find your provider in the Identity-Based Auth section
- Click the provider to open its configuration panel
- Enter the required credentials (varies by provider)
- Toggle the provider On
- Click Save
After enabling an auth provider, configure your Allowed Origins (CORS) in Settings → Security to allow token exchange requests from your frontend domain.
Disabling a Provider
Toggle the provider switch Off in the Authentication page. Existing connections authenticated via this provider will remain active until they disconnect.
Next Steps
- Token Exchange API - How to implement the backend token exchange flow
- ACL with Identity Bindings - Use identity variables in access control policies