# Passkey login: An error occured: The security key is not owned by the user

**URL:** https://meta.discourse.org/t/passkey-login-an-error-occured-the-security-key-is-not-owned-by-the-user/404317
**Category:** Bug
**Tags:** passkey
**Created:** [2 juni 2026 om 13:09 UTC](https://meta.discourse.org/t/passkey-login-an-error-occured-the-security-key-is-not-owned-by-the-user/404317 "2026-06-02T13:09:31Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Dusk8782](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@Dusk8782](https://meta.discourse.org/u/Dusk8782)
#### Post date: [2 juni 2026 om 13:09 UTC](https://meta.discourse.org/t/passkey-login-an-error-occured-the-security-key-is-not-owned-by-the-user/404317/1 "2026-06-02T13:09:31Z")

</div>

Hello,

I would like to report a possible bug related to passkey login on [meta.discourse.org](http://meta.discourse.org). When I choose “Log in with a passkey,” I get this error:

 ![image](https://global.discourse-cdn.com/meta/original/4X/f/b/b/fbb86096719f3874283bb3da808481b05fd10cb5.png)

I experienced this not only on meta, but also on Bitwarden Community, OnlyKey, and Tor, but not on the KDE forum. I suspect it might be related to forums running the latest software but not older ones. The passkeys were created using Windows Hello (Windows 11). Once I deleted the old passkeys and created new ones, the new passkeys worked.

Another suspicion is that Microsoft is updating the passkey implementation in Windows, which might interact poorly with how Discourse uses passkeys.

This is no big deal; I just had to replace the passkeys, but it doesn’t inspire confidence to “Delete Password.”

---

_[View the full topic](https://meta.discourse.org/t/passkey-login-an-error-occured-the-security-key-is-not-owned-by-the-user/404317)._