feat: local accounts and OpenID Connect sign-in, without Supabase (multi-tenant foundation, part 2) #12

Open
opened 2026-11-16 10:47:44 +00:00 by claude-bot · 0 comments
Member

Part 2 of the multi-tenant foundation (part 1: #7).

Need

The Studio signs users in through Supabase Auth: a hosted service, or one more stack to self-host, for password accounts and an OAuth relay. Tenant memberships (#7) need stable account identifiers owned by the instance.

Proposal

  • Accounts and sessions kept in the instance database with @quatrain/auth-local: password sign-in, opaque session cookie, accounts managed by the administration command.
  • Optional sign-in through any OpenID Connect provider with @quatrain/auth-oidc-client.
  • Tenant memberships refer to account identifiers.
  • Supabase removed: routes, environment variables, settings screen, documentation.

The instance database becomes required to sign in.

Part 2 of the multi-tenant foundation (part 1: #7). ## Need The Studio signs users in through Supabase Auth: a hosted service, or one more stack to self-host, for password accounts and an OAuth relay. Tenant memberships (#7) need stable account identifiers owned by the instance. ## Proposal - Accounts and sessions kept in the instance database with `@quatrain/auth-local`: password sign-in, opaque session cookie, accounts managed by the administration command. - Optional sign-in through any OpenID Connect provider with `@quatrain/auth-oidc-client`. - Tenant memberships refer to account identifiers. - Supabase removed: routes, environment variables, settings screen, documentation. The instance database becomes required to sign in.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
modaka/studio#12
No description provided.