Today's archie authenticates people: users, organisations, passkeys, OIDC, API tokens, roles and the access engine. The new binary has a bootstrap admin token and people records only, so nothing that needs a real user identity (chat, approvals by login, any hosted use) can land.
Move them as modules of the one binary: an identity module (users, orgs, identities, tokens), the passkey and OIDC login flows, and the access checks the dashboard and API already rely on. The admin token stays as bootstrap only.
Done when: a person signs in with a passkey and with OIDC on the new binary, their token is scoped to their role, and the old access tables are migrated or explicitly retired.
Today's archie authenticates people: users, organisations, passkeys, OIDC, API tokens, roles and the access engine. The new binary has a bootstrap admin token and people records only, so nothing that needs a real user identity (chat, approvals by login, any hosted use) can land.
Move them as modules of the one binary: an identity module (users, orgs, identities, tokens), the passkey and OIDC login flows, and the access checks the dashboard and API already rely on. The admin token stays as bootstrap only.
Done when: a person signs in with a passkey and with OIDC on the new binary, their token is scoped to their role, and the old access tables are migrated or explicitly retired.
sam
added the featurehigh labels 2026-11-16 01:24:27 +00:00
Part of epic #1977. The dependency could not be recorded: this Gitea's dependency write endpoint answers 404 and the connector that used to add it is disconnected, so this comment carries the link.
Part of epic #1977. The dependency could not be recorded: this Gitea's dependency write endpoint answers 404 and the connector that used to add it is disconnected, so this comment carries the link.
Benched: whether OIDC, LDAP and SAML ship as identity-provider extensions, with passkeys and sessions staying in core, waits on the maintainer's decision. This issue stays open until that decision lands.
Benched: whether OIDC, LDAP and SAML ship as identity-provider extensions, with passkeys and sessions staying in core, waits on the maintainer's decision. This issue stays open until that decision lands.
Sign-in on the binary: password, passkey, recovery, setup, sign-out, personal tokens and capabilities, served to the Vue dashboard; OIDC copied but not yet run against a provider. Non-admins can only reach their own account until per-route permissions exist. Commit c12f6b794.
Sign-in on the binary: password, passkey, recovery, setup, sign-out, personal tokens and capabilities, served to the Vue dashboard; OIDC copied but not yet run against a provider. Non-admins can only reach their own account until per-route permissions exist. Commit c12f6b794.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Today's archie authenticates people: users, organisations, passkeys, OIDC, API tokens, roles and the access engine. The new binary has a bootstrap admin token and people records only, so nothing that needs a real user identity (chat, approvals by login, any hosted use) can land.
Move them as modules of the one binary: an identity module (users, orgs, identities, tokens), the passkey and OIDC login flows, and the access checks the dashboard and API already rely on. The admin token stays as bootstrap only.
Done when: a person signs in with a passkey and with OIDC on the new binary, their token is scoped to their role, and the old access tables are migrated or explicitly retired.
Part of epic #1977. The dependency could not be recorded: this Gitea's dependency write endpoint answers 404 and the connector that used to add it is disconnected, so this comment carries the link.
Benched: whether OIDC, LDAP and SAML ship as identity-provider extensions, with passkeys and sessions staying in core, waits on the maintainer's decision. This issue stays open until that decision lands.
Sign-in on the binary: password, passkey, recovery, setup, sign-out, personal tokens and capabilities, served to the Vue dashboard; OIDC copied but not yet run against a provider. Non-admins can only reach their own account until per-route permissions exist. Commit
c12f6b794.