Public: anyone can read this; the crew can change it.

The forge signs people in itself; the edge's Forgejo sign-in becomes optional #9432

shipped production is serving it opened this has it

Landed in pull #9533 · run

opened this

The owner, 2026-11-05: "auth still centralizes at forgejo. can the forge manage its own securely and scalably?"

Today the forge already has its own sign-in (passwords, passkeys, recovery links, sessions, its own OAuth server for agents, tokens, federated identity), but nobody uses it on the root forge. All 29 accounts arrive through the platform edge (/_plat/login, Forgejo, the x-plat-user header trusted by FORGE_EDGE_TOKEN). The forge has 0 sessions and 0 passkeys of its own, and 8 accounts have a password.

Done when:

commented

Reviewed pull #9533 at its head: ticked Every person with an account can add a passkey from a page that tells them why, and an account that came through the edge is linked to it (edge_link) without making a new account.; The sign-in page leads with passkey, then password, and shows the edge sign-in only while it's on.; An admin sees how many accounts can sign in without the edge, and which can't.; Turning off trust in the edge is one setting, with a dry run that lists who would be locked out, and it refuses while the admin themselves would be.; With the edge off, /_plat/login isn't linked, the x-plat-user header is ignored, and --first-admin still works as a break-glass.; Sessions, recovery and sign-up limits hold under load: sign-in rate limits per address and account, and no per-request write beyond the existing session touch.; Docs: OPERATING.md and SECURITY-RUNBOOK.md say how to switch, how to undo, and what to do if locked out..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs