Tender Surrender

When implementing passkeys yourself or investigating how passkeys work on other websites, setting up a debugger to capture requests and responses or parsing binaries to read the contents is not easy. You can easily achieve this using a Chrome Extension called WebAuthn DevTools.

At the FIDO Tokyo Seminar, I was told it's hard to track the high-level picture of how passkeys are evolving, and I thought it would be helpful to introduce key terminologies so you can get a grasp of the passkey world and look into more details when necessary. So here it is.

I have revamped my blog. While the visual design remains largely the same, I added an English version through multilingual support (i18n) and updated the underlying infrastructure.

I wrote a book titled 「パスキーのすべて」 (Everything About Passkeys). Here is a brief introduction to what's inside the book, which will be released on January 28th.

Lately, I have been seeing complaints that passkeys are hard to use. I have also observed several posts from people who were in trouble because they couldn't sign in to a service they wanted to use, simply because the passkey they were sure they had created could not be found.

So in this blog post, I'd like to explore why this happens, how to avoid such situations, what actions users can take, and what service providers can do to reduce the number of users who feel this way.