Repository navigation
supabase-dashboard 0.3.0-dev.7
Pre-releaseWhat's new
Signing out of the provider signs out of the dashboard. The dashboard now supports OpenID Connect Back-Channel Logout 1.0. When an operator signs out of Authentik, Authentik sends a signed logout token to /auth/oidc/backchannel-logout. The dashboard then ends the sessions started by signing in through Authentik, and the Studio sessions opened from them. Password sessions of the same account stay signed in.
The token's signature, issuer, audience, age and logout event are checked, and a token with a nonce is refused. Each token works only once. The endpoint accepts no cookie, takes a form of at most 16 KiB, and is exempt from the same-origin check only for POST to that path. Each ended session is in the audit log as session.oidc_backchannel_logout, without the token. To turn it on, set the provider's Logout URI to https://<dashboard host>/auth/oidc/backchannel-logout with the Back-channel method; the startup log prints the URL. Checked in Chromium against Authentik 2026.8.5.
Admins can unlink an operator's identity. On the administrator page's account list, an installation admin can unlink another operator's OIDC identity after a confirmation that names the account. This ends only the sessions started with that identity, and it's audited. Admins unlink their own identity under Account settings, as before.
Upgrading from 0.3.0-dev.6
- Back up the metadata database.
- Set
SUPABASE_DASHBOARD_VERSION=0.3.0-dev.7, thendocker compose pull && docker compose up -d. One migration runs at startup. It records which provider sign-in started each session, so sessions that already exist aren't ended by a logout from the provider. - To use back-channel logout, add the Logout URI in Authentik as above. Authentik must be able to reach the dashboard's public URL.
Known limitations
- Used logout tokens are remembered in the dashboard's memory, so a restart or a second dashboard instance doesn't know about them.
- Ending Studio sessions through a provider logout was tested against a mock provider, not with Authentik.
- Provider groups don't map to organization roles yet, and only one provider can be configured.
Container image (linux/amd64, linux/arm64):
docker pull ghcr.io/filipnone/supabase-dashboard:0.3.0-dev.7
To deploy on a Linux server with Docker, download supabase-dashboard-0.3.0-dev.7-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.6...v0.3.0-dev.7
Full Changelog: v0.3.0-dev.6...v0.3.0-dev.7