Connectors

Supabase connector

Let Limenia ban and unban Supabase Auth users directly when moderators suspend, ban or restore a user.

Like every connector, it works in addition to the webhook and never replaces it; your app still enforces restrictions itself. An admin sets it up in the dashboard (tab Connectors).

What it does

Calls PUT /auth/v1/admin/users/{id} of your project with ban_duration: ban_user → 876000h; suspend_user → the remaining seconds until suspendUntil; restore (account) and the end of a suspension → none. Limenia never deletes users.

Requirements

The externalUserId is the Supabase user UUID (auth.users.id).

Setup

Create a separate secret key (sb_secret_…, name e.g. limenia) in Supabase, enter the project URL (https://<ref>.supabase.co, origin only) and the key, enable and press Test connection. Legacy JWT keys (service_role) are not accepted.

The stored key is bound to the host of the project URL: if you change the URL to another host, enter the key again. Limenia never sends a stored key to a new host. Test connection waits up to 5 seconds and can be repeated after 10 seconds.

Session lifetime

Supabase cannot end sessions by user ID: an issued access token stays valid until it expires (default up to one hour). Where bans must take effect immediately, check with getUser() (asks the auth server) instead of getClaims().

Errors in the delivery log

Code Meaning Retried?
user_not_found No user with this UUID: the externalUserId is not the Supabase user ID no
supabase_unauthorized The secret key is wrong or was deleted no
supabase_rejected Supabase rejected the request no
blocked_url The project URL is not a public https address no
project_not_found The project URL does not point to a Supabase project yes
not_configured The connector was switched off or is incomplete no
timeout, connection_failed, unavailable Supabase did not answer in time or is unavailable yes