Block a device from the Devices list, the Users list or the user profile
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- authorization, full-stack, security
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Block a connected device → it disconnects immediately and the Access column shows Blocked.
- The blocked device tries to connect to a location without posture checks → it's rejected.
- The client of the blocked device shows the Blocked badge and the Device blocked screen.
- Block a device from the Users list and from the user profile → the result is the same as from the Devices list.
- Dominant language
- Rust
- Stars
- 2.9k
- Forks
- 119
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 63
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DefGuard/defguard
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in DefGuard/defguard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
chroma-core/chroma#7879 ·
Maintainers usually reply within 1 day
-
priority middle
Difficulty 1/5 Under an hour Newbie friendliness 72/100
KATO-Hiro/AtCoderClans#12838 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day