automatically disable inactive users based on VPN activity

未关闭
  • 哪里不对？
#4,022 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
authentication, security

调研方向

Start by tracing how successful VPN authentications and WireGuard handshakes are recorded, then find where Core Settings are defined and how user accounts are disabled and reactivated. The issue names no files or tests, so identify the relevant entry points and existing audit logging before estimating the work. Done means an opt-in configurable inactivity policy uses the latest activity across a user's devices, records automatic deactivations, and permits manual reactivation.

由索引模型根据 Issue 内容生成。

描述

feature

Feature request

Description

Add an option in Defguard Core to automatically disable user accounts after a configurable period of VPN inactivity.

This would improve security by ensuring that unused VPN accounts do not remain active indefinitely.

Expected behavior
  • Default inactivity period: 30 days
  • Configurable threshold: Allow administrators to configure the inactivity period (e.g. 7, 30, 60, 90 days).
  • Automatic deactivation: Disable users who have had no successful VPN authentication or WireGuard handshake within the configured period.
  • Activity tracking: Both successful VPN authentications and WireGuard handshakes should reset the inactivity counter.
  • Multiple devices: Activity on any registered device should reset the inactivity counter for the entire user account.
  • Audit logging: Log automatic deactivations with a timestamp and reason.
  • Manual reactivation: Allow administrators to reactivate disabled accounts.
Suggested implementation

Add a global setting under Core Settings:

Automatically disable inactive users

  • Enabled / disabled (disabled by default)
  • Inactivity threshold: 30 days (default)
  • Optional: Exclude specific users or groups from automatic deactivation

A user should be considered active whenever:

  1. They successfully authenticate to the VPN.
  2. Any of their registered devices completes a successful WireGuard handshake.

The inactivity period should be calculated from the most recent of these events.

Optional enhancement: device-level inactivity

Extend the same functionality to individual devices.

For example, a device that has not successfully authenticated or completed a WireGuard handshake for 30 days could automatically be disabled without affecting the user's other devices.

Device-level inactivity thresholds could be configured independently from user-level settings.

Benefits
  • Reduces the number of unused active VPN accounts.
  • Prevents active VPN users from being incorrectly deactivated.
  • Improves security by limiting access through abandoned accounts and devices.
  • Reduces manual administrative effort.
  • Helps enforce access lifecycle and security policies.
主要语言
Rust
星标
2.9k
派生
121
平均合并
20 小时 19 分钟
30 天内合并 PR
76

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

DefGuard/defguard 的其他 Issue

查看 DefGuard/defguard 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。