mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #1383] [FEATURE REQUEST] inactive account timeout #484
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#484
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @h-2 on GitHub (Jan 19, 2026).
Original GitHub issue: https://github.com/lldap/lldap/issues/1383
Motivation
I have a bunch of services that I offer to friends and family. Every so often, I talk to someone, and I am like: "You can do that without Google/Meta/...! Here, I will quickly set you up with an account, and you can try it out."
Sometimes the person will keep using my service(s). Often they won't (which is also fine). But then I have idle accounts which are needless attack surface.
Describe the solution you'd like
I'd like to have one of the following (in order of preference):
departed."inactivity" == time without successful login
Ideally, there would also be:
Ideally, there would also be an e-mail sent notifying the user (either before or after).
Describe alternatives you've considered
I have been told that this is difficult to do for LDAP servers, because they usually don't track logins. I have also been told that certain clients can do this, but I don't see that solving my problem. I don't want to track usage of specific services; it's totally fine and desired that some users will only use some services.
Additional context
I would guess that people who selfhost would appreciate such a feature? It would really help "server hygiene".
@nitnelave commented on GitHub (Jan 19, 2026):
I'd leave that to a plugin, once we finish implementing the API. It should be relatively simple to implement (an LLM should be able to do that given proper docs).