DashboardAuthentication
Authentication
Configure how devices and applications authenticate with your MQTT broker
CloudSignal supports three authentication methods. You can use one or combine multiple methods depending on your use case.
Authentication Methods
Auth Providers (Recommended)
Connect your existing identity provider - Supabase, Firebase, Auth0, or Clerk. Users authenticate with their existing accounts, no separate MQTT passwords needed.
Token Auth
Generate temporary server-side tokens with 60-minute TTL. Best for backend-to-device connections where your server controls access.
Client Credentials
Create static username/password pairs. Best for dedicated devices with persistent connections.
Choosing a Method
| Method | Best For | Password Management | Session Duration |
|---|---|---|---|
| Auth Providers | Web/mobile apps with existing auth | None (token exchange) | Session-based |
| Token Auth | Server-to-device, IoT fleets | Auto-generated, auto-expired | 60 minutes |
| Client Credentials | Dedicated devices, testing | Manual | Persistent |
Auth Providers are recommended for production applications. They eliminate the need to manage MQTT passwords separately from your application's user accounts.