automatically disable inactive users based on VPN activity

Aperta
  • Qualcosa non va?
#4,022 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
authentication, security

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Rust
Stelle
2.9k
Fork
121
Merge medio
20h 19m
PR unite (30g)
76

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DefGuard/defguard

Tutte le issue di DefGuard/defguard

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.