automatically disable inactive users based on VPN activity

Abierto
  • ¿Algo no está bien?
#4,022 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
authentication, security

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Rust
Estrellas
2.9k
Forks
121
Merge medio
20 h 19 min
PR fusionados (30 d)
76

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DefGuard/defguard

Todos los issues de DefGuard/defguard

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.