automatically disable inactive users based on VPN activity

オープン
  • 何か問題がありますか？
#4,022 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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分
マージ済み PR（30日）
76

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

DefGuard/defguard のほかの issue

DefGuard/defguard の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。