Skip to content

Incorrect handling of updated_at - #49

Merged
yaleman merged 2 commits into
kanidm:mainfrom
Firstyear:20260219-resolve-invalid-updated-at
Feb 19, 2026
Merged

yaleman merged 2 commits into
kanidm:mainfrom
Firstyear:20260219-resolve-invalid-updated-at

Conversation

@Firstyear

Copy link
Copy Markdown
Member

The field updated_at was not marked with the correct serde attributes which caused it to be serialised as null, and required to be present during deserialisation.

Fixes #48 .

  • cargo fmt has been run
  • cargo test has been run and passes
  • documentation has been updated with relevant examples (if relevant)

The field updated_at was not marked with the correct serde attributes
which caused it to be serialised as null, and required to be present
during deserialisation.
@Firstyear
Firstyear requested a review from yaleman February 19, 2026 04:52
@yaleman
yaleman merged commit b227a0d into kanidm:main Feb 19, 2026
1 check passed
@Firstyear
Firstyear deleted the 20260219-resolve-invalid-updated-at branch February 19, 2026 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Invalid JWT is issued wrt updated_at header

2 participants