[GH-ISSUE #898] [FEATURE REQUEST] modifyTimestamp #328

New issue

Closed

opened 2026-02-27 08:16:40 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 08:16:40 +03:00

Owner

Originally created by @nitnelave on GitHub (Apr 20, 2024).
Original GitHub issue: https://github.com/lldap/lldap/issues/898

Originally assigned to: @Copilot on GitHub.

Motivation
SSSD requires it.

Describe the solution you'd like
A custom rust-implemented field that gets updated whenever a user/group is modified

Describe alternatives you've considered
You can create a custom attribute by hand, but not realistically keep it up to date.

Originally created by @nitnelave on GitHub (Apr 20, 2024). Original GitHub issue: https://github.com/lldap/lldap/issues/898 Originally assigned to: @Copilot on GitHub. **Motivation** SSSD requires it. **Describe the solution you'd like** A custom rust-implemented field that gets updated whenever a user/group is modified **Describe alternatives you've considered** You can create a custom attribute by hand, but not realistically keep it up to date.

kerem

2026-02-27 08:16:40 +03:00

closed this issue
added the
enhancement

good first issue

help wanted

frontend

backend

ldap

rust
labels

kerem commented

2026-02-27 08:16:41 +03:00

Author

Owner

@dregad commented on GitHub (Dec 26, 2024):

I need this too.

@dregad commented on GitHub (Dec 26, 2024): I need this too.

kerem commented

2026-02-27 08:16:41 +03:00

Author

Owner

@nitnelave commented on GitHub (Aug 26, 2025):

Implementation overview:

create a DB migration that adds a new timestamp "user modified" column with default value of now. Do the same for "password modified"
update the user model to include the new fields
add them as hardcoded, read-only attributes in the LDAP and GraphQL APIs
update the SQL backend handlers to update them on user modification
display them in the user details page in the frontend

@nitnelave commented on GitHub (Aug 26, 2025): Implementation overview: - create a DB migration that adds a new timestamp "user modified" column with default value of now. Do the same for "password modified" - update the user model to include the new fields - add them as hardcoded, read-only attributes in the LDAP and GraphQL APIs - update the SQL backend handlers to update them on user modification - display them in the user details page in the frontend