[GH-ISSUE #1299] [BUG] pwdChangedTime is returned in the wrong format #452

New issue

Closed

opened 2026-02-27 08:17:22 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 08:17:22 +03:00

Owner

Originally created by @YotamKorah on GitHub (Sep 21, 2025).
Original GitHub issue: https://github.com/lldap/lldap/issues/1299

Originally assigned to: @Copilot on GitHub.

Describe the bug
When querying for pwdChangedTime, the timestamp is returned in the rfc3339 format instead of the expected and standerdized format of GeneralizedTime.

To Reproduce
I configured LLDAP as a user federation in keycloak as described in the examples in this repo. when going to the credentials page of a user the page crashes and an exception is thrown.
In the logs of the keycloak server (with loglevel set to trace) i found that the value was incorrectly formatted.

Expected behavior
pwdChangedTime should be returned in the GeneralizedTime format

Logs
No relevant logs from lldap, for the keycloak logs, look here

Originally created by @YotamKorah on GitHub (Sep 21, 2025). Original GitHub issue: https://github.com/lldap/lldap/issues/1299 Originally assigned to: @Copilot on GitHub. **Describe the bug** When querying for pwdChangedTime, the timestamp is returned in the rfc3339 format instead of the expected [and standerdized](https://ldapwiki.com/wiki/Wiki.jsp?page=PwdChangedTime) format of GeneralizedTime. **To Reproduce** I configured LLDAP as a user federation in keycloak as described in the examples in this repo. when going to the credentials page of a user the page crashes and an exception is thrown. In the logs of the keycloak server (with loglevel set to trace) i found that the value was incorrectly formatted. **Expected behavior** pwdChangedTime should be returned in the GeneralizedTime format **Logs** No relevant logs from lldap, for the keycloak logs, look [here](https://github.com/keycloak/keycloak/issues/42592)

kerem

2026-02-27 08:17:22 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 08:17:23 +03:00

Author

Owner

@nitnelave commented on GitHub (Sep 21, 2025):

Thanks for the issue! That's indeed a clear-cut bug, let me have a stab at it.

@nitnelave commented on GitHub (Sep 21, 2025): Thanks for the issue! That's indeed a clear-cut bug, let me have a stab at it.

kerem referenced this issue

2026-02-27 09:09:36 +03:00

[PR #452] [MERGED] docker: fix healthcheck #752