ProtonMail / ProtonMail/WebClients
Allow passkeys for insecure domain (`localhost`)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
Description
We are happy to answer your questions about the code or discuss technical ideas.
Please complete the following checklist (by adding [x]):
- I have searched open and closed issues for duplicates
- This isn't a feature request
- This is not a report about my app not working as expected
Hi,
I would like to test an application with authenticators that are backed up like the ones managed by ProtonPass.
During the registration process, I am facing the following message:
failed to generate passkey: InsecureLocalhostNotAllowed
Please note that the browser (Chrome 126) considers the domain is secure (HTTPS with a trusted root CA).
❓ Question: How to allow the creation of passkeys on localhost? Is there any option to turn on/off?
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.
Research direction
Start by tracing the passkey registration entry point that produces the InsecureLocalhostNotAllowed error, then check how localhost, HTTPS, and trusted certificates are handled. Reproduce the behavior with Chrome 126 and a trusted HTTPS certificate; done means passkey creation works on localhost or the supported configuration is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, security, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100