<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Webauthn on jfx's site</title><link>https://jfx.ac/tags/webauthn/</link><description>Recent content in Webauthn on jfx's site</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 20 Dec 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://jfx.ac/tags/webauthn/index.xml" rel="self" type="application/rss+xml"/><item><title>WebAuthn in the CLI</title><link>https://jfx.ac/blog/webauthn-in-the-cli/</link><pubDate>Fri, 20 Dec 2024 00:00:00 +0000</pubDate><guid>https://jfx.ac/blog/webauthn-in-the-cli/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;The first thing that often comes to mind about FIDO2 WebAuthn clients is their integration with modern web browsers. Typically, users are prompted on a website to verify their identity by entering a PIN and interacting with a physical security key. This user-friendly flow is designed to to be fast, secure, and reduce reliance on passwords.&lt;/p&gt;
&lt;p&gt;But what if you need to implement this functionality outside of a browser? What if your application runs in a command-line interface (CLI)? The good news is this is possible, but it&amp;rsquo;s not well documented or commonly implemented. I was motivated to implement this as leaving a terminal and waiting for a page to load to tap a device seemed wasteful.&lt;/p&gt;</description></item></channel></rss>