Local accounts: display-name field, served through /api/v1/user-names #729

Closed
opened 2026-09-25 01:49:37 +00:00 by Cordy · 0 comments
Owner

Follow-up from #727 (found during the v0.6.268 dogfood pass): display names resolve from the directory (Keycloak first/last name), but local accounts have no name fields at all, so they always fall back to usernames — and there is nowhere on the instance to enter one.

Scope:

  • local-users.json records gain an optional displayName (statestore-persisted like the rest).
  • Users & access → Accounts (the #533 surface): a "Display name" input on create, and an edit affordance on existing local accounts.
  • /api/v1/user-names merges local display names over the directory map (local wins for local accounts; directory users unaffected).
  • Fallback behaviour unchanged: no display name → username, everywhere.
  • i18n ×4 for the new labels; audit the change under the existing local-user verbs.

Deliberately its own red-green run: it touches the local-account store and the admin accounts surface, not the #727 rendering paths.

Follow-up from #727 (found during the v0.6.268 dogfood pass): display names resolve from the directory (Keycloak first/last name), but **local accounts have no name fields at all**, so they always fall back to usernames — and there is nowhere on the instance to enter one. Scope: - `local-users.json` records gain an optional `displayName` (statestore-persisted like the rest). - Users & access → Accounts (the #533 surface): a "Display name" input on create, and an edit affordance on existing local accounts. - `/api/v1/user-names` merges local display names over the directory map (local wins for local accounts; directory users unaffected). - Fallback behaviour unchanged: no display name → username, everywhere. - i18n ×4 for the new labels; audit the change under the existing local-user verbs. Deliberately its own red-green run: it touches the local-account store and the admin accounts surface, not the #727 rendering paths.
Cordy closed this issue 2026-10-01 20:55:25 +00:00
Sign in to join this conversation.
No labels
No project
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#729
No description provided.