Show the verification code in the desktop client
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- authentication, desktop, security
Research direction
No files or tests are named. Start by locating the desktop client's device-status and verification entry points, then trace the core and admin-panel verification flow. Use the six listed scenarios to validate the badges, screen states, synchronized code, clipboard action, cancellation, and successful verification; resolve the open question about an uninitiated verification.
Written by the indexing model from the issue text.
Description
User story
As a desktop client user, I want to see the verification code in the app, so that I can read it to my admin and get my device verified.
Acceptance criteria
- An attested, not verified device shows a "Verify" badge in the header, in both the tray view and the full window.
- Clicking the badge opens the Device verification screen, which shows an explanation, the six numbers, the countdown, "Copy code to clipboard", and Close.
- The client decrypts the code received from the core with the TPM-bound key, and the code refreshes in sync with the admin panel.
- After the admin verifies, the client shows "Verification status updating", then "Device successfully verified" with a Got it button.
- A verified device shows a "Verified" badge and has no verification entry point.
- After the admin cancels, the client closes the verification screen and keeps the Verify badge.
Test scenarios
- The admin initiates verification and the user opens the Verify screen → both show the same code.
- Wait 60 seconds → the code changes on both sides at the same time.
- Click "Copy code to clipboard" → the clipboard contains the six numbers.
- The admin clicks Verify → the client shows the success screen, then the Verified badge.
- The admin cancels → the client closes the verification screen and the Verify badge remains.
- On a verified device → the badge shows Verified and clicking it opens nothing.
Open questions
- What should the client show if the user opens the Verify screen before the admin has initiated verification?
- Dominant language
- Rust
- Stars
- 2.9k
- Forks
- 121
- Avg merge
- 22h 6m
- Merged PRs (30d)
- 64
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
-
Set focus to PIN field after user clicks connect when MFA method is security key (UX improvement)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
DefGuard/defguard#3851 · 2 comments ·
Maintainers usually reply within 1 day
-
Invalid hover on the OS delete in posture check edit formPossibly taken @jakub-tldr claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
DefGuard/defguard#3842 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Prevent setting "Defguard URL" and "Defguard public URL" to the same addressPossibly taken @jakub-tldr claimed this 2 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DefGuard/defguard#3751 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in DefGuard/defguard
Similar issues
-
area:ecosystem documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Chelis-Lang/chelis#3866 ·
Maintainers usually reply within 1 day
-
bug documentation sev-0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dekobon/big-code-analysis#1620 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100