feat(admin): remove the SSO link of an account whose provider changed its subject

A sign-in with another subject of the same provider is refused, so an
account whose provider re-issued the subject (a migrated or rebuilt IdP, a
changed sub format) was locked out: editing the email, as the wiki advised,
never touched the stored link. The edit dialog now offers "Remove SSO link"
for other accounts while SSO is set up (DELETE /api/admin/users/:id/sso,
audit admin.user_sso_unlink). The next SSO sign-in links again under the
rules of a first one, so it still needs a verified, not self-set email.
The log line names the remedy, and the wiki tells the two refusals apart.

Fixes #3065
This commit is contained in:
Maurice
2026-11-12 15:39:21 +01:00
parent a3a4f7cf79
commit b53130ca0d
43 changed files with 415 additions and 9 deletions
@@ -823,6 +823,14 @@ export class UsersRepository extends TrekRepository<Users> {
await this.nativeUpdate({ id }, { oidc_sub: sub, oidc_issuer: issuer });
}
/**
* `UPDATE users SET oidc_sub = NULL, oidc_issuer = NULL WHERE id = ?`: the
* admin's "Remove SSO link" (#3065). No `updated_at`, like the link it undoes.
*/
async clearOidcIdentity(id: number): Promise<void> {
await this.nativeUpdate({ id }, { oidc_sub: null, oidc_issuer: null });
}
// ---------------------------------------------------------------------
// O8 — claims-based role change
// ---------------------------------------------------------------------