[tracking] QSP-7 User might use untrusted authenticators
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- authentication, frontend, security
Research direction
Start at the UI flow for creating an identity via a hardware authenticator; the issue does not name a file or test. Locate where authenticator setup copy is rendered, add guidance to use recommended security keys, and verify the resulting message in that flow.
Written by the indexing model from the issue text.
Description
- add copy to UI when creating an identity via hardware authenticator to use recommended security keys
cc @fmorency @hansl
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor 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 liftedinit/alberto
-
enhancement
liftedinit/alberto#142 · 4 comments · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
liftedinit/alberto#141 ·
-
e2e testing in CI Openenhancement
Difficulty 4/5 3-5 days Newbie friendliness 20/100
liftedinit/alberto#125 ·
All issues in liftedinit/alberto
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
bcgov/bc-wallet-mobile#4761 · 1 comment ·
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100