Memberships beside Kanidm: the invite makes the account too

Kanidm makes people, portal makes members. A site can switch to
memberships before its sign-in provider is one everyone already has.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GT37Z1Xtfd9pUuQtMTg6Yt
This commit is contained in:
Bendik Aagaard Lynghaug
2026-09-30 14:06:55 +02:00
co-authored by Claude Fable 5.1
parent 5bc021de77
commit c4e2de5efa
3 changed files with 28 additions and 5 deletions
+5 -4
View File
@@ -64,10 +64,11 @@ Unset, a `KANIDM_API_TOKEN` means Kanidm and no token means
memberships. With memberships:
- A desk invite writes an `invited` record and mails "log in at the
site, and your place is there". No account is made: the provider
makes people, portal makes members. So the provider has to be one
everyone can already sign in to, which is what Vipps Login is for a
Norwegian association, and what Kanidm is not.
site, and your place is there". The provider makes people, portal
makes members: with Vipps Login everyone can already sign in. A
Kanidm still configured beside memberships (`KANIDM_API_TOKEN`)
makes the account too, with no group and the one-time link in the
mail, so a site can switch to memberships before its provider does.
- `grants` writes a record for the person the case is about, from the
form's name and phone number or address.
- `SEED_ADMIN_PHONE` or `SEED_ADMIN_EMAIL` writes the first person's.