Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Block a device from the Devices list, the Users list

Abierto
  • ¿Algo no está bien?
#3,733 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
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
authorization, full-stack, security

Línea de trabajo

Trace the Devices list, Users list, user profile, verification modal, client connection handling, access decision, and Activity log entry points. Start by mapping how device access and verification status are represented across the admin and client surfaces. Done means every listed action and test scenario works, including immediate disconnection, blocked access, client feedback, re-verification, and activity logging.

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

Descripción

User story

As an admin, I want to block a device, so that it immediately loses access.

Acceptance criteria
  • The "Block device" action is in the Devices row menu, the drawer Actions, the Verification modal, the user's devices in the Users list, and the Devices tab of the user profile.
  • The action is available regardless of attestation or verification status.
  • The action opens the "Block device" confirmation modal: "Are you sure you want to block this device? It will immediately lose access and remain blocked until it is verified again." The modal has Cancel and Block buttons.
  • After blocking, the device's active connections are dropped, Access shows "Blocked", and the device can't connect to any location, regardless of posture checks.
  • The client shows a "Blocked" badge and the "Device blocked" screen with a Got it button.
  • The admin can initiate verification for a blocked, attested device.
  • The Activity log records the block.
Test scenarios
  1. Block a connected device → it disconnects immediately and the Access column shows Blocked.
  2. The blocked device tries to connect to a location without posture checks → it's rejected.
  3. The client of the blocked device shows the Blocked badge and the Device blocked screen.
  4. Block a device from the Users list and from the user profile → the result is the same as from the Devices list.
Lenguaje dominante
Rust
Estrellas
2.9k
Forks
121
Merge medio
22 h 47 min
PR fusionados (30 d)
62

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.