Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Thoughts on UX

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
authentication, security

Research direction

No files, tests, or entry points are named. First map the existing passkey and account-recovery flows, then resolve the proposals around forgotten, replaced, and newly added passkeys, including the Boolean ID and local-storage concerns. Done requires an agreed UX and security design before implementation.

Written by the indexing model from the issue text.

Description

Forgot Passkey

  • instead of "Forgot Password?" have "Can't Access Passkey?"

Replace Passkey

  • this will make any encrypted storage permanently inaccessible

Adding a Passkey

  • send magic email or text message to allow it
  • use password to allow it? maybe not?
  • allow creating password if the device doesn't support WebAuthn at all

Boolean IDs

IDs are a huge pain in the butt:

  • the os keychain may or may not be synced between devices
  • the current device may or may not have synced with the os keychain
  • the current browser on that device may or may not access the system keychain
  • the current browser may or may not be synced with its own key storage
  • if you've saved IDs to the server, you can't use them as entropy for local encryption
  • you can't retrieve IDs from the server without the user ALREADY being logged in
    (otherwise anyone can just grab bunches of IDs for your users, or you have waaay more logic to handle in regards to fingerprinting the user's devices and browsers, etc to ensure that you don't pass them out willy-nilly)
  • the IDs are only useful to prevent creation of the same ID, which you get by logging in - otherwise, if you had them, you would already know

THEREFORE, it seems like each device should just have some sort of localStorage that simply indicates a tiny piece of information about each key - such as if the "attestation" issuer is a security key or os keycahin, etc.

Dominant language
JavaScript
Stars
2
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BeyondCodeBootcamp/passkeys

All issues in BeyondCodeBootcamp/passkeys

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.