app-owned Admins and Users for non idP provided instances #533
Closed
opened 2026-09-14 00:37:22 +00:00 by Cordy
·
12 comments
No Branch/Tag specified
main
b12v07
b11v07
b10v07
ci-rc-publish
fx15-s3dry
b9v07
b8v07
bench742
b7v07
legal-texts-v0.2
b6v07
b5v07
b4v07
b3v07
sx1139
st742
b2v07
ix1102
fu1098
zp1097
wd1099
tr1100
qf1077
nc1070
ci1
rp1072
lk1073
ab1071
fi1074
si1070
ra1054
wo1056
oc1057
tf1055
sv1063
fg1059
st1058
fs929
mu1039
ls1033
cf975
lf835
dx1023
ml896
a11y2
av1022
r913
r7
r6
r5
r45
r23
r1
b10
b9
fix-b5
fix-b4
fix-b3
fix-b2
fix-b1
fix-922
fix-923
fix-911
fix-343b
batch-a
v0.6.413
v0.6.412
v0.6.411
v0.6.410
v0.6.409
v0.6.408
v0.6.407
v0.6.406
v0.6.405
v0.6.404
v0.6.403
v0.6.402
v0.6.401
v0.6.400
v0.6.399
v0.6.398
v0.6.397
v0.6.396
v0.6.395
v0.6.394
v0.6.393
v0.6.392
v0.6.391
v0.6.390
v0.6.389
v0.6.388
v0.6.387
v0.6.386
v0.6.385
v0.6.384
v0.6.383
v0.6.382
v0.6.381
v0.6.380
v0.6.379
v0.6.378
v0.6.377
v0.6.376
v0.6.375
v0.6.374
v0.6.373
v0.6.372
v0.6.371
v0.6.370
v0.6.369
v0.6.368
v0.6.367
v0.6.366
v0.6.365
v0.6.364
v0.6.363
v0.6.362
v0.6.361
v0.6.360
v0.6.359
v0.6.358
v0.6.357
v0.6.356
v0.6.355
v0.6.354
v0.6.353
v0.6.352
v0.6.351
v0.6.350
v0.6.349
v0.6.348
v0.6.347
v0.6.346
v0.6.345
v0.6.344
v0.6.343
v0.6.342
v0.6.341
v0.6.340
v0.6.339
v0.6.338
v0.6.337
v0.6.336
v0.6.335
v0.6.334
v0.6.333
v0.6.332
v0.6.331
v0.6.330
v0.6.329
v0.6.328
v0.6.327
v0.6.326
v0.6.325
v0.6.324
v0.6.323
v0.6.322
v0.6.321
v0.6.320
v0.6.319
v0.6.318
v0.6.317
v0.6.316
v0.6.315
v0.6.314
v0.6.313
v0.6.312
v0.6.311
v0.6.310
v0.6.309
v0.6.308
v0.6.307
v0.6.306
v0.6.305
v0.6.304
v0.6.303
v0.6.302
v0.6.301
v0.6.300
v0.6.299
v0.6.298
v0.6.297
v0.6.296
v0.6.295
v0.6.294
v0.6.293
v0.6.292
v0.6.291
v0.6.290
v0.6.289
v0.6.288
v0.6.287
v0.6.286
v0.6.285
v0.6.284
v0.6.283
v0.6.282
v0.6.281
v0.6.280
v0.6.279
v0.6.278
v0.6.277
v0.6.276
v0.6.275
v0.6.274
v0.6.273
v0.6.272
v0.6.271
v0.6.270
v0.6.269
v0.6.268
v0.6.267
v0.6.266
v0.6.265
v0.6.264
v0.6.263
v0.6.262
v0.6.261
v0.6.260
v0.6.259
v0.6.258
v0.6.257
v0.6.256
v0.6.255
v0.6.254
v0.6.253
v0.6.252
v0.6.251
v0.6.250
v0.6.249
v0.6.248
v0.6.247
v0.6.246
v0.6.245
v0.6.244
v0.6.243
v0.6.242
v0.6.241
v0.6.240
v0.6.239
v0.6.238
v0.6.237
v0.6.236
v0.6.235
v0.6.234
v0.6.233
v0.6.232
v0.6.231
v0.6.230
v0.6.229
v0.6.228
v0.6.227
v0.6.226
v0.6.225
v0.6.224
v0.6.223
v0.6.222
v0.6.221
v0.6.220
v0.6.219
v0.6.218
v0.6.217
v0.6.216
v0.6.215
v0.6.214
v0.6.213
v0.6.212
v0.6.211
v0.6.210
v0.6.209
v0.6.208
v0.6.207
v0.6.206
v0.6.205
v0.6.204
v0.6.203
v0.6.202
v0.6.201
v0.6.200
v0.6.199
v0.6.198
v0.6.197
v0.6.196
v0.6.195
v0.6.194
v0.6.193
v0.6.192
v0.6.191
v0.6.190
v0.6.189
v0.6.188
v0.6.187
v0.6.186
v0.6.185
v0.6.184
v0.6.183
v0.6.182
v0.6.181
v0.6.180
v0.6.179
v0.6.178
v0.6.177
v0.6.176
v0.6.175
v0.6.174
v0.6.173
v0.6.172
v0.6.171
v0.6.170
v0.6.169
v0.6.168
v0.6.167
v0.6.166
v0.6.165
v0.6.164
v0.6.163
v0.6.162
v0.6.161
v0.6.160
v0.6.159
v0.6.158
v0.6.157
v0.6.156
v0.6.155
v0.6.154
v0.6.153
v0.6.152
v0.6.151
v0.6.150
v0.6.149
v0.6.148
v0.6.147
v0.6.146
v0.6.145
v0.6.144
v0.6.143
v0.6.142
v0.6.141
v0.6.140
v0.6.139
v0.6.138
v0.6.137
v0.6.136
v0.6.135
v0.6.134
v0.6.133
v0.6.132
v0.6.131
v0.6.130
v0.6.129
v0.6.128
v0.6.127
v0.6.126
v0.6.125
v0.6.124
v0.6.123
v0.6.122
v0.6.121
v0.6.120
v0.6.119
v0.6.118
v0.6.117
v0.6.116
v0.6.115
v0.6.114
v0.6.113
v0.6.112
v0.6.111
v0.6.110
v0.6.109
v0.6.108
v0.6.107
v0.6.106
v0.6.105
v0.6.104
v0.6.103
v0.6.102
v0.6.101
v0.6.100
v0.6.99
v0.6.98
v0.6.97
v0.6.96
v0.6.95
v0.6.94
v0.6.93
v0.6.92
v0.6.91
v0.6.90
v0.6.89
v0.6.88
v0.6.87
v0.6.86
v0.6.85
v0.6.84
v0.6.83
v0.6.82
v0.6.81
v0.6.80
v0.6.79
v0.6.78
v0.6.77
v0.6.76
v0.6.75
v0.6.74
v0.6.73
v0.6.72
v0.6.71
v0.6.70
v0.6.69
v0.6.68
v0.6.67
v0.6.66
v0.6.65
v0.6.64
v0.6.63
v0.6.62
v0.6.61
v0.6.60
v0.6.59
v0.6.58
v0.6.57
v0.6.56
v0.6.55
v0.6.54
v0.6.53
v0.6.52
v0.6.51
v0.6.50
v0.6.49
v0.6.48
v0.6.47
v0.6.46
v0.6.45
v0.6.44
v0.6.43
v0.6.42
v0.6.41
v0.6.40
v0.6.39
v0.6.38
v0.6.37
v0.6.36
v0.6.35
v0.6.34
v0.6.33
v0.6.32
v0.6.31
v0.6.30
v0.6.29
v0.6.28
v0.6.25
v0.6.24
v0.6.23
v0.6.22
v0.6.21
v0.6.20
v0.6.19
v0.6.18
v0.6.17
v0.6.16
v0.6.15
v0.6.14
v0.6.12
v0.6.11
v0.6.10
v0.6.9
v0.6.8
v0.6.7
v0.6.6
v0.6.5
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.7
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
v0.4.12
v0.4.11
v0.4.10
v0.4.9
v0.4.8
v0.4.7
v0.4.6
v0.4.5
v0.4.4
v0.4.3
v0.4.2
v0.4.1
v0.3.30
v0.3.29
v0.3.28
v0.3.27
v0.3.26
v0.3.25
v0.3.24
v0.3.23
v0.3.22
v0.3.21
v0.3.20
v0.3.19
v0.3.18
v0.3.17
v0.3.16
v0.3.15
v0.3.14
v0.3.13
v0.3.12
v0.3.11
v0.3.10
v0.3.9
v0.3.8
v0.3.7
v0.3.6
v0.3.5
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.0.3
v0.0.2
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".
No due date set.
Dependencies
No dependencies set.
Reference: Cordy/Cairn#533
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
— after talking with Manuel, we should have a Local Cairn admin available on deploy. On launch and at the setup wizard, ask the user to configure a local Cairn admin which is stored there. If no idP is provided during setup or conf file or environment (don’t remember anymore where we set this) then an additional tab should render under the admins dashboard called “Users & Groups” where local user can be managed up to 50 users total. There Users and groups and admins can be defined locally.
here is the conversation i had with Manuel about it:
[9/13/26, 7:39:03 PM] Manuel Novak: Aber AD, Keycloak, local User (inkl. Admin) müssen halt sitzen zu 100%
[9/13/26, 7:39:45 PM] Manuel Novak: Und eine Mischung aus lokalem Admin und wahlweise externen Diensten (AD/Keycloak)
[9/13/26, 7:39:52 PM] You: true, ich weis ich bin über das mit local user kurz drüber geballert. aber das war n kurzer run. and denke auch nur admin relevant.
[9/13/26, 7:40:15 PM] You: wollen wir app-owner user managment within admin dashboard of cairn?
[9/13/26, 7:40:27 PM] You: das ziel ist ja eigentlich keine app-owned user zu haben?
[9/13/26, 7:41:08 PM] Manuel Novak: Nur die lokale Liste mit Admins und unserem 25 Userlimit
[9/13/26, 7:41:22 PM] Manuel Novak: Mach einfach ne harte Grenze mit lokalen Nutzern
[9/13/26, 7:41:32 PM] You: 25 userlimit?
[9/13/26, 7:41:49 PM] You: ah damn dann muss ich aber vlt schauen ob ich das in ner json haben will oder lieber ne kleine db :')
[9/13/26, 7:42:19 PM] You: hätte gesagt, 1 admin user can be inside, that's that. keycloak ist ja auch n schmaller footprint
[9/13/26, 7:42:21 PM] You: +
[9/13/26, 7:42:28 PM] Manuel Novak: JSON lokal bis total 35User (10x Admins + 25 free User) is noch ok
[9/13/26, 7:42:41 PM] Manuel Novak: Nah ein Admin reicht nicht
[9/13/26, 7:42:47 PM] You: ich denke grad, wegen der PQ keys, will man die in der json habe :')
[9/13/26, 7:43:24 PM] Manuel Novak: Ist deren Problem dann und es muss nur dokumentiert sein, dass man lieber externe Dienste nutzen sollte
[9/13/26, 7:43:42 PM] Manuel Novak: Weil eben die JSON Plaintext is
[9/13/26, 7:44:47 PM] Manuel Novak: Im normalen Betrieb wird die JSON 1-3 Admins für den Notfall drin haben und alle anderen Admins sind im AD/Keycloak
[9/13/26, 7:45:37 PM] You: hm ja, gut, doch kann ich noch reinlunzen, aber dann entweder später heute als Phone UI. entweder heute später in der nacht oder morgen kommt der freeze
[9/13/26, 7:46:43 PM] Manuel Novak: Keine Hektik. Es muss sauber funktionieren
[9/13/26, 7:47:14 PM] You: yesss, also immernoch beta hier :D cute v0.8 erst für fully ready for release und last code freeze
[9/13/26, 7:47:29 PM] Manuel Novak: Wenn ein MA das Ding das erste Mal deployed und bei der Authentifizierung Probleme hat, wirkt das schlecht
[9/13/26, 7:47:38 PM] You: valid
[9/13/26, 7:48:13 PM] Manuel Novak: Ich hab mir Mokapi für AD mal angeschaut. Ich lass eine Instanz dagegen mal authen
[9/13/26, 7:48:20 PM] You: ich lasse es halt save noch in der v0.7 milestone, da code-review noch geballert wird, vulnerability hunting, und so weiter.
[9/13/26, 7:49:07 PM] You: so mit allem zusammen denke ich nicht das da v0.7 milestone geclosed wird in unter 2-3 wochen
[9/13/26, 7:50:45 PM] You: es flashed mich grad irwie weil ich irgendwie nichtmal selber erwartet habe heute "fertig" zu werden
[9/13/26, 7:51:11 PM] You: hab einfach geballert und bemerkt "oh ich hab nurnoch den phoneUI pass übrig, damn"
[9/13/26, 7:51:42 PM] Manuel Novak: Feinschliff is immer und wir müssen den kompletten UseCase von einem 0815 MA durchspielen und optimieren von:
[9/13/26, 7:51:50 PM] You: ganz kurz.
[9/13/26, 7:52:27 PM] You: die local users, + local admins. sollen die nur available sein wenn kein idP vorhanden ist? im sinne von Cairn was not served an idP
[9/13/26, 7:52:45 PM] You: renders "Users and groups" tab aufm admin dashboard dann aber auch nur dann
[9/13/26, 7:52:50 PM] Manuel Novak: Nah lokale Admins muss es IMMER geben können
[9/13/26, 7:53:03 PM] You: admins werden konfiguriert on deployment.
[9/13/26, 7:53:09 PM] Manuel Novak: Yes
[9/13/26, 7:53:14 PM] You: initial launch will ask to set a password on webUI
[9/13/26, 7:53:26 PM] Manuel Novak: Tönt gut
[9/13/26, 7:53:27 PM] You: und da wollen wir 1-3 oder nur 1?
[9/13/26, 7:54:04 PM] Manuel Novak: 1-3 aber die anderen 2x kann der initial Admin setzen ohne Wizard beim Deployment
[9/13/26, 7:54:51 PM] Manuel Novak: Wenn es dann um AD/KC User geht --> die müssen auch promoted/demoted werden können
[9/13/26, 7:55:06 PM] Manuel Novak: Die lokalen Admins sind wie gesagt nur Notfall Logins
[9/13/26, 7:55:50 PM] Manuel Novak: Zusätzlich arbeiten die meisten MA mit ihrem Admin-AD Account der auch in der Admin Cairngruppe sein muss aber nicht lokal ist
[9/13/26, 7:56:51 PM] Manuel Novak: Mit den lokalen Admin Accounts wird nur initial alles eingerichtet und gefixt im Fehlerfall aber DailyBusiness wird damit nicht gemacht
[9/13/26, 7:58:04 PM] Manuel Novak: Zumindest ist es im Banken/Versicherung/kantonalen/militärischen Umfeld verboten nicht-zentral verwaltete Accounts mit erhöhten Rechten für alltägliche Aufgaben zu nutzen
Distilled the conversation with Manuel into requirements, checked against what already exists in the code.
Requirements as I read them:
What already exists (more than we remembered): auth mode
"local"is fully implemented (auth.NewLocal(users).WithStore(...), argon2id PHC viacairnd hash-password);LocalUsersPathdefaults to/data/.cairn/local-users.jsonand already persists runtime-created users — the first-run setup admin from #51;CAIRN_ADMIN_*env-ensured local admin exists (#310);local-users.jsonis already in the #153 state-in-backend set, so it survives redeploys. The gaps: (a) in OIDC mode there is no local password login at all today (pwLoginis only wired when mode != "oidc") — requirement 1 needs a local-login path that coexists with the IdP redirect flow; (b) no Users & Groups admin UI, no runtime CRUD API, no caps; (c) no promote/demote surface (admins are a config allow-list); (d) local "groups" have no defined backing — presumably the existingspacestore(local spaces with write/read roles, IdP-less path) is the natural home rather than a second group system.Two things I need from you before mockup/spec:
/login?local) so end users never see it? Banking/military context in Manuel's messages suggests the quiet route, but that's a guess.Also flagging for the spec: seat accounting (do local users consume licence seats the same as IdP users — presumably yes), per-user encryption custody for local users (keycloak-profile custody can't serve them; openbao and deployment custody can — worth a compatibility note), and the promote/demote audit trail (seat-release already writes audit entries; admin changes should too).
Decision (Nikola, 2026-09-14): the hard limit is 50 local users total (supersedes the 35 from the chat excerpt). Emergency-login UX question still open.
Decisions (Nikola, 2026-09-14):
#admin/users/access— either extending that topic or a new tab beside it: create users and admins, basic permissions, for the initial admin.Next: competitor deep dive (how Nextcloud / OpenCloud / Seafile / Pydio and break-glass patterns elsewhere handle initial admin + local-login-beside-SSO + local user management), then a full user-flow mockup for review.
Competitor research + code recon — the design basis for the mockup.
How the field handles it:
Initial admin at deploy. Three patterns exist: env-var before first start (oCIS
INITIAL_ADMIN_PASSWORD— set-once, changes silently ignored later, a documented footgun; GrafanaGF_SECURITY_ADMIN_*); default credentials with forced change (Grafanaadmin/admin— universally criticised); and a browser wizard on first run (Portainer, Nextcloud installer). Portainer's wizard has the unclaimed-instance problem — anyone who reaches the fresh instance first becomes admin — which it patches with a 5-minute timeout. Cairn's existing #51 flow already beats all of these:/setupis a browser wizard, but guarded by a one-time token printed only to the operator's log, so "whoever races first" cannot claim the instance and there's no set-once env trap. We keep it and extend it; nothing to copy here.Local login beside SSO. Nextcloud hides the local form behind
/login?direct=1— the support forums are full of admins who couldn't find it during an IdP outage, and their own security note warns the hidden route still exposes stale local passwords (hiding ≠ protection). Seafile keeps the classic form visible next to the SSO button. Grafana shows SSO buttons above the form and lets youdisable_login_form— after which a broken IdP means editing config on disk to get back in. Nikola's visible-link decision matches the Seafile/Grafana-default pattern and dodges Nextcloud's documented confusion; the security answer to "visible = exposed" is few, admin-managed, argon2id-hashed local accounts + the existing verify limiter + audit, not hiding the door.Local users beside a directory. oCIS bundles a minimal LDAP (IDM) it explicitly positions for "small environments up to a few hundred users" — precedent for our 50 cap and for treating built-in accounts as a first-class small-deployment mode, not a degraded one. Pydio keeps an internal user repo and auto-files externally-authenticated users into a separate group — mirrors how our seats list already tracks seen IdP users, which gives the promote/demote UI its user list for free.
Code recon — what exists (more than the issue assumed):
#admin/users/accessalready exists: admin topicusers, tabsaccess|seats, pane#adm-usersvialoadUsers(). The new UI grows inside the existing Access tab — no new topic needed./setup(#51) is a real page (setup.html) +POST /setup: token check, username validation, ≥10-char password,store.Create(username, hash, admin=true), closes permanently once a user exists. Gated today on local mode only (pwLogin != nil+ empty store + no config users).LocalStore(local-users.json, statestore-backed so it survives redeploys per #153):storedUser{PasswordHash, Admin, CreatedAt}— Create/lookup/Empty only. Needs List / Delete / SetPassword / SetAdmin + the 50 cap./storage-setup, same token mechanism) — the wizard chain becomes: storage → first admin → done.Implementation shape this points to (the mockup follows it):
pwLogin, which gets wired in OIDC mode via the existingauth.Multipattern (app-passwords already stack this way).user-create,user-remove,user-password-reset,admin-promote,admin-demote) — the #433 registry guard will enforce registration.Sources: Nextcloud direct-login discussion, nextcloud-oidc-login README, OpenCloud external IdP docs, oCIS IDM service docs, Seafile SSO setup, Pydio manage users, Grafana admin+SSO thread, Grafana disable login form.
Mockup with the full flow follows for review.
Wave 1 shipped — v0.6.194 (PR #545), live on both dogfoods.
Backend complete per the approved mockup: LocalStore CRUD + 50-cap + last-sign-in stamp, AdminStore for runtime directory-admin grants (both in the #153 state set — boot now shows
files=18), local accounts +/setupin every auth mode,POST /auth/passwordlive in OIDC via the Multi stack,WithAdminFlagRuntimeunion, the full/api/v1/admin/local-users+directory-admins+/api/v1/me/passwordAPI with last-admin/self guards, and five new audit verbs (the #433 guard caught my parameterized helper and forced literals at call sites — working as designed).Live proof on files-bao (OIDC, empty local store):
FIRST-RUN SETUP available — open /setup and paste this one-time tokenin the boot log. Both dogfoods are now claimable: grab the token from each pod's log (kubectl logs -n cairn deploy/cairn-openbao | grep FIRST-RUN) and create your break-glass admin athttps://files-bao.c0rdyceps.ch/setup— that will also be the wave-2/3 test account. Until claimed,/setupwaits harmlessly behind the token.Wave 2 (login + setup pages) next, then wave 3 (Access tab UI).
All three waves shipped — v0.6.194 / .195 / .196 (PRs #545, #546, #547), live on both dogfoods.
The full approved flow is now real:
/setupgate widened,POST /auth/passwordin OIDC, full admin API with guards and five audited verbs./login#localdeep link, back link; setup page with repeat-password and closes-permanently copy. (One flagged deviation: no storage→admin stepper — the page can't know whether the storage wizard ran.)Your verification pass (both dogfoods are unclaimed — each restart mints a fresh token):
kubectl logs -n cairn deploy/cairn-openbao | grep FIRST-RUN→ openhttps://files-bao.c0rdyceps.ch/setup, paste the token, create your break-glass admin (you land signed in).#admin/users/access→ your local account listed (1 of 50), add a test account with the generated password, reset it, promote/demote, remove; check the audit query showsuser-createetc.nikola-test(and any seen user) with Make admin.Still open on this issue: docs handbook page "Running without an identity provider" (plaintext-JSON note, 1–3 emergency admins guidance — Manuel's requirement 5), phone-view polish of the new Access sections if your #389 pass finds issues, and Manuel's own run-through before closing. The self-service password-change UI (backend
/api/v1/me/passwordexists) also has no surface in the user menu yet — small follow-up.Stepper follow-up — v0.6.198… correction: v0.6.197 (PR #548), live.
Nikola's suspicion after seeing
/setupon files-bao: the "Set up this Cairn" title + Storage ✓ → Administrator stepper from the mockup only appear on truly new instances. Reality check: the stepper had not been implemented at all — the flagged wave-2 deviation ("the page cannot know whether the storage wizard ran"). That call was wrong: main already knows, becausestorageSource == "bootstrap"means the D11 wizard wrote the pointer.Fixed:
/setup/statusnow carriesstorageWizard(TDD, witnessed red), and the setup page conditionally titles itself "Set up this Cairn" with the mockup's stepper only when the storage wizard actually ran first. Config-provisioned instances (both dogfoods) keep the plain first-run page — honest either way. So the behaviour Nikola expected is now the behaviour that exists, verifiable on the fresh wizard-deployed test instance planned in a few days.Also confirmed live meanwhile:
/setupon files-bao redirects to/login(setup claimed and closed permanently), the claimed admin survived the v0.6.196→197 redeploy via the state backend, and the login page shows the wave-2 SSO + local-account layout.v0.6.198 shipped (PR #549) — login/setup mockup fidelity, per Nikola's screenshot comparison.
Root cause of the visual drift was a CSS cascade bug, not missing markup:
.divider { display:flex }was declared after.hidden { display:none }, so at equal specificity the later rule won and the "or" divider stayed visible in the revealed local-account state. Fixed with a compound selector.divider.hidden { display:none }.The same bug existed latently in setup.html —
.steps { display:flex }after.hiddenmeant the v0.6.197 wizard stepper would have shown on every instance instead of only wizard-deployed ones (exactly backwards). Fixed the same way (.steps.hidden) before anyone saw it; the conditional logic itself was already correct.Fidelity changes on both pages:
.frowpattern, left-aligned), inputs on surface white with slightly taller padding. Setup's password requirement moved into a muted label suffix "(at least 10 characters)".#msgmargin and card bottom padding tightened).Live-verified on files-bao at
/login#local: labelled fields, no divider, back link + note with tight spacing; and the default state still shows SSO button + divider + local-account link with form/back/note hidden. The setup-page changes ride along for the fresh test instance in a few days.v0.6.204 shipped (PR #557, live on both dogfoods) — the last build item on this issue is done.
The user menu gains Change password: current/new/repeat with inline validation (mismatch, under 10 characters, wrong current password), backed by the
POST /api/v1/me/passwordendpoint that has existed since wave 1. On an SSO account the dialog answers with "Your password is managed by your identity provider, not by Cairn" instead of a raw 409. i18n ×4.Also in this release, from Nikola's Accounts-tab dogfooding (#552 thread): creating a local account named like a seen directory account is now refused with an inline explanation — the two would share one identity, so a password sign-in would have reached the directory user's files (a security catch, not just UX; local re-creations and config admins are exempt); and group member adds gained autocomplete + validation via
GET /api/v1/admin/groups/candidates.What remains on #533 is verification, not code: Nikola's fresh-instance wizard pass (stepper, token flow, setup closing) on the upcoming test deployment, and Manuel's run-through of the no-IdP story (docs at
docs/handbook/local-accounts.md). Once those pass, this can close.QA pass by Claude (2026-10-03, local build of main @ v0.6.317, 127.0.0.1, throwaway accounts).
This covers the fresh-instance wizard (storage → admin → closing) and the no-IdP story from
docs/handbook/local-accounts.md, with deliberate attempts to break both. It does not replace Nikola's and Manuel's manual passes. OIDC mode was not exercised (no local IdP).Works as intended
storage.driver: "setup"):/redirects to/storage-setup./setupby itself.storageWizard:true.<root>/.cairnis not reachable through the file API.Findings
High: credential and session revocation
auth.Local.verified(internal/auth/auth.go ~105-122) caches a fingerprint of the last accepted password per user.LocalStore.SetPasswordandDeletenever clear it.POST /api/v1/me/password, the old password still signs in through the form and over WebDAV Basic (207). This lasts until someone signs in with the new password or the process restarts.auth/session.go)./api/v1/meand lists files./api/v1/admin/*(200).Medium
.and..(and control characters such as tab and newline) are accepted as usernames.auth.validUsername)...would be unusable..,..and non-printable characters at validation./auth/passwordor WebDAV Basic. 30 wrong guesses took about 30 ms each, and the right password still worked afterwards. There is no per-IP or per-account delay or lockout (Nextcloud uses brute-force throttling).user-create,admin-promoteetc. entries until someone enables audit.local-accounts.md("What is audited") doesn't say this.victimandVICTIMcan coexist as two accounts. This is confusing in lists, and on a case-insensitive host filesystem their homes would collide.Low / UX
http://192.168.10.32:3900, the homelab Garage address shipped in product UI./setupand/loginhave no language selector at all, while/storage-setuphas four languages./setupafter closure goes to the login withnext=/setup, and after signing in shows a raw "404 page not found". It should land on home.restart: unless-stopped). A baredocker runwithout a restart policy just stops. Worth a line in deployment.md.POST /setupdecodes an unbounded body (noMaxBytesReader) while setup is pending; storage-setup caps at 64 KiB.Findings 1 and 2 are the ones I'd fix before closing this issue. 3 to 6 are candidates for v0.7. The rest are polish.
The QA findings above are filed, all in v0.7:
Each issue holds the repro, the research and a plan, plus the decisions that are open for Nikola.
Closing check (2026-10-09)
The five requirements from the Manuel conversation, checked against main (v0.6.324):
/setupwork in local, LDAP and OIDC modes, and the dogfoods (OIDC) have local accounts./setupis token-guarded and closes for good once an admin exists (#852).MaxLocalUsers = 50(internal/auth/localstore.go); the cap was QA'd under parallel creates.docs/handbook/local-accounts.md, with the three account sources made explicit in #846.The 2026-10-03 QA findings are all shipped and closed:
Since then, in the same area:
Still open, each in its own issue, so it no longer needs this parent:
/setupafter closure, restart copy, body cap).Closing as done.