All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Understanding WebAuthn credential protection policy and discoverable credentials

By

mooreds

7d ago· 3 min readenInsight

Summary

This article explains the WebAuthn credential protection policy, specifically how developers can use the `residentKey` option to control whether credentials are discoverable. It discusses the limitations of relying parties in controlling when or how credentials can be discovered, and the need for user verification before making credentials discoverable to prevent account snooping.

Key quotes

· 3 pulled
When creating a WebAuthn credential, you can specify whether it should be discoverable using the residentKey option.
However, the relying party cannot control when or how the credential can be discovered.
You may want it to become discoverable only after user verification and hide the account's existence from snooping users.
Snippet from the RSS feed
Pilcrow's personal website.

You might also wanna read