# 어떤 디스코urs에서도 패스키를 설정할 수 없습니다

**URL:** https://meta.discourse.org/t/cant-set-up-passkey-on-any-discourse/397642
**Category:** Bug
**Tags:** passkey, fixed
**Created:** [3월 4, 2026, 6:14오후 UTC](https://meta.discourse.org/t/cant-set-up-passkey-on-any-discourse/397642 "2026-03-04T18:14:26Z")
**Posts on this page:** 1
**Showing post:** 18

<div class="post-metadata">

### Author: ![keegan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/keegan/32/383395_2.png) [@keegan](https://meta.discourse.org/u/keegan)
#### Post date: [3월 5, 2026, 5:53오후 UTC](https://meta.discourse.org/t/cant-set-up-passkey-on-any-discourse/397642/18 "2026-03-05T17:53:35Z")

</div>

@agr 님이 이 문제를 찾아내주셔서 감사합니다. 여기 수정 사항을 반영했습니다:

> <https://github.com/discourse/discourse/pull/38266>
>
> \*\*Currently, passkey registration has two bugs:\*\*
> 1. Registration fails with …an HTTP 500 for authenticators that include extension data (i.e. \`hmac-secret\` in their attestation response) because we slice all bytes after the credential ID the public key.
> 2. Registration fails with \`NotAllowedError\` on some hardware keys (i.e. Solo 2) because \`pubKeyCredParams\` includes invalid HMAC symmetric algorithms from the \`COSE\` gem, which strict authenticator firmware rejects.
> 
> \*\*This fix:\*\*
> 1. Uses \`CBOR::Unpacker\` streaming decode to read exactly one \`CBOR\` object from the byte stream, stopping before any trailing extension data. Also adds \`COSE::MalformedKeyError\` to the rescue block so future failures return a proper error response.
> 2. Replaces the blanket \`COSE::Algorithm.registered\_algorithm\_ids\` with an explicit list of asymmetric signature algorithms valid for \`WebAuthn\`.
> 
> Meta bug report: https://meta.discourse.org/t/cant-set-up-passkey-on-any-discourse/397642/

Discourse를 최신 버전으로 업데이트하면 이제 문제가 해결되어야 하지만, 그래도 문제가 발생하면 알려주세요.

---

_[View the full topic](https://meta.discourse.org/t/cant-set-up-passkey-on-any-discourse/397642)._