<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Passkeys on Commentary of Takao</title><link>https://takao.blog/en/tags/passkeys/</link><description>Recent content in Passkeys on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/passkeys/index.xml" rel="self" type="application/rss+xml"/><item><title>WebAuthn and Passkeys: Passwordless Authentication in 2024</title><link>https://takao.blog/en/web/webauthn-passkeys/</link><pubDate>Tue, 02 Apr 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/webauthn-passkeys/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post WebAuthn and Passkeys: Passwordless Authentication in 2024" /&gt;&lt;p&gt;Passwords have been the primary authentication mechanism for decades, but they come with well-documented security and usability problems. WebAuthn (Web Authentication) and the emerging passkey ecosystem promise to replace passwords with cryptographically secure, phishing-resistant authentication. As of 2024, passkey support has reached critical mass across all major platforms, making this the ideal time to implement passwordless authentication.&lt;/p&gt;
&lt;h2 id="understanding-webauthn"&gt;Understanding WebAuthn
&lt;/h2&gt;&lt;p&gt;WebAuthn is a W3C standard that enables public-key cryptography-based authentication on the web. The core flow involves two operations: registration and authentication. During registration, the server sends a cryptographic challenge to the client, the authenticator creates a new key pair, and the public key is stored on the server. During authentication, the server sends a challenge, the authenticator signs it with the private key, and the server verifies the signature against the stored public key.&lt;/p&gt;</description></item></channel></rss>