fix(kanidm): force shortname for uid/gid attr map on unixd v2 #495

Closed
lytedev wants to merge 1 commit from fix-kanidm-uid-attr-map into main
Owner

Summary

Kanidm 1.10's unixd config v2 changed the default uid_attr_map / gid_attr_map from name to spn, so users started resolving as daniel@idm.h.lyte.dev instead of daniel. This broke local tooling assuming the bare shortname.

Pin both to "name" at the top level of unixSettings (they're top-level fields in v2; only pam_allowed_login_groups sits under [kanidm]). Verified against the kanidm source at the pinned commit c070a411 (v1.10.0-dev).

Test plan

  • Deploy to thinker
  • id daniel and getent passwd daniel resolve the kanidm user as bare daniel
  • SSH login as daniel still works
## Summary Kanidm 1.10's `unixd` config v2 changed the default `uid_attr_map` / `gid_attr_map` from `name` to `spn`, so users started resolving as `daniel@idm.h.lyte.dev` instead of `daniel`. This broke local tooling assuming the bare shortname. Pin both to `"name"` at the top level of `unixSettings` (they're top-level fields in v2; only `pam_allowed_login_groups` sits under `[kanidm]`). Verified against the kanidm source at the pinned commit `c070a411` (v1.10.0-dev). ## Test plan - [ ] Deploy to thinker - [ ] `id daniel` and `getent passwd daniel` resolve the kanidm user as bare `daniel` - [ ] SSH login as `daniel` still works
fix(kanidm): force shortname for uid/gid attr map on kanidm 1.10 unixd v2
Some checks failed
/ build (push) Waiting to run
/ check-format (push) Has been cancelled
6bc26dd084
Kanidm 1.10's unixd config v2 changed the default uid_attr_map/gid_attr_map
to "spn", causing users to resolve as "name@idm.h.lyte.dev" instead of
"name". Pin both to "name" to restore pre-upgrade behavior.
lytedev closed this pull request 2026-04-20 10:54:52 -05:00
Some checks failed
/ build (push) Waiting to run
Required
Details
/ check-format (push) Has been cancelled
Required
Details

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
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
lytedev/nix!495
No description provided.