Skip to content

supabase-dashboard 0.3.0-dev.6

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 15 Nov 21:48
· 4 commits to main since this release

What's new

Single sign-on through OpenID Connect. Operators can sign in through an OIDC provider such as Authentik. It's off unless SUPABASE_DASHBOARD_OIDC_ISSUER_URL is set, and passwords keep working with it on. A provider identity signs in only to the account it was linked to. Each operator links theirs under Account settings > Security after signing in with their password, and can unlink it there. The dashboard never finds, links or creates accounts by email, so the provider can't sign anyone up.

The sign-in uses the authorization code flow with PKCE, state and nonce, and checks the ID token's issuer, audience, signature and expiry through the openidconnect crate. The dashboard only contacts the issuer's own origin. It follows no redirects, uses no proxy, and limits the size and time of each answer. A sign-in that started in one browser can't be finished in another. The setup steps for Authentik, and the redirect URI to register, are in "Signing in with OIDC" in docs/deployment.md. The flow was checked in Chromium against Authentik 2026.8.5.

Changing the sign-in email. Under Account settings, operators can change the address they sign in with. They confirm their current password, and the dashboard emails a one-time link to the new address. The address changes only when that link is used, and the old address gets a notice. A link expires, works once, and stops working if a newer one is sent or the password changes. Confirming also cancels any password reset link sent to the old address. This needs mail set up; without it, the page says so.

Invitations after signing in. An invitee who already has an account but isn't signed in now comes back to the invitation after signing in, and no longer has to open the email link again. The invitation code stays in the browser's session storage until it's used and never appears in a URL or the server log.

Upgrading from 0.3.0-dev.5

  1. Back up the metadata database.
  2. Set SUPABASE_DASHBOARD_VERSION=0.3.0-dev.6, then docker compose pull && docker compose up -d. The server applies two migrations at startup: one for email change requests and one for linked OIDC identities.
  3. To turn on single sign-on, follow "Signing in with OIDC". The settings are in the new lines of .env.example, and the client secret goes in a Compose secret like the encryption key.

Known limitations

  • Signing out of the provider doesn't sign out of the dashboard yet (no back-channel logout), and provider groups don't map to organization roles.
  • Only one provider can be configured, and only through the deployment's settings.
  • A sign-in in progress is kept in the dashboard's memory. A restart cancels it, and several dashboard instances behind one address can't share it.
  • An installation admin can't unlink another operator's identity.
  • If the provider's callback fails, the page the operator was going to is lost.
  • Changing the email needs mail set up. The limit of five change requests an hour resets when the server restarts. Other sessions stay signed in after the change.

Container image (linux/amd64, linux/arm64):

docker pull ghcr.io/filipnone/supabase-dashboard:0.3.0-dev.6

To deploy on a Linux server with Docker, download supabase-dashboard-0.3.0-dev.6-docker.tar.gz, unpack it, and follow its README. Nothing is compiled on the server.

The *-linux-gnu.tar.gz files contain the same server binary and web assets for running without Docker (glibc 2.36 or newer).

This is a development pre-release. Expect breaking changes between dev releases. Database migrations only move forward: back up the metadata database before upgrading, and do not downgrade.

Full Changelog: v0.3.0-dev.5...v0.3.0-dev.6

Full Changelog: v0.3.0-dev.5...v0.3.0-dev.6