feat(auth): add OIDC multi-user mode - #334
Open
saltbo wants to merge 2 commits into
Open
Conversation
realmroot
Bot
force-pushed
the
codex/oidc
branch
from
August 15, 2026 06:15
3dff180 to
499b1ba
Compare
saltbo
marked this pull request as ready for review
August 15, 2026 06:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This adds an optional, lightweight multi-user mode backed by an external OpenID Connect provider. Sink does not add local user registration or user-management screens.
rootownerroot, with an explicit owner-alias option for identity transitionsRelated to #104.
Why
The existing discussions around multi-user support point toward external identity rather than building a local user-management system. This keeps the scope focused on small-team deployments while preserving the current single-user behavior for existing installations.
Authentication modes
OIDC mode is selected only when the issuer, client ID, client secret, and session secret are all configured. The modes never run side by side.
Existing single-user deployments require no migration beyond the included D1 schema migration, which assigns existing links to the
rootowner.Validation
pnpm exec vitest run: 32 files, 304 tests passedpnpm types:checkpnpm locales:check: 11 locales, 8 modulespnpm buildA full
pnpm lintalso scans two unchanged Pages deployment documents from the current base branch and reports their existing formatting errors. This PR deliberately leaves those unrelated files untouched.