[GH-ISSUE #52] Question : lastLogonTimestamp not available #31

Open
opened 2026-02-27 16:47:43 +03:00 by kerem · 0 comments
Owner

Originally created by @advissor on GitHub (Mar 16, 2024).
Original GitHub issue: https://github.com/rroemhild/docker-test-openldap/issues/52

Hi,
I was trying to test locally scenario of disabling users that hasn't logged on for a while via AD based on lastLogonTimestamp

Though, after login via LDAP (ldapsearch and python client), I can see that in list of attributes

I guess this is the AD setting

Any quick fix to enable this or code change that can be done?

P.S: I've seen on the web that this timestamp can lag and is not always the most reliable. But, as there are not many other alternatives to do this via LDAP, still want to try this approach. Poweshell on server is not an option at the moment

Thanks!

Originally created by @advissor on GitHub (Mar 16, 2024). Original GitHub issue: https://github.com/rroemhild/docker-test-openldap/issues/52 Hi, I was trying to test locally scenario of disabling users that hasn't logged on for a while via AD based on lastLogonTimestamp Though, after login via LDAP (ldapsearch and python client), I can see that in list of attributes I guess this is the AD setting Any quick fix to enable this or code change that can be done? P.S: I've seen on the web that this timestamp can lag and is not always the most reliable. But, as there are not many other alternatives to do this via LDAP, still want to try this approach. Poweshell on server is not an option at the moment Thanks!
Sign in to join this conversation.
No labels
pull-request
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
starred/docker-test-openldap#31
No description provided.