- From: Martin Kreichgauer via GitHub <noreply@w3.org>
- Date: Fri, 30 May 2025 00:20:16 +0000
- To: public-webauthn@w3.org
> There's now two mentions of "matching username" in this issue. Are these in reference to matching on [`PublicKeyCredentialEntity.name`](https://w3c.github.io/webauthn/#dom-publickeycredentialentity-name) (`user.name`), or for [`PublicKeyCredentialUserEntity.id`](https://w3c.github.io/webauthn/#dom-publickeycredentialuserentity-id) (`user.id`)? Sorry, yes, I meant matching user.**id**. (Updated the original post to clarify.) Sounds like the consensus here is that conditional create should just behave like regular create. I agree that's probably the most predictable behavior, and as long as we can align all the implementations accordingly, that works for me. -- GitHub Notification of comment by kreichgauer Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2296#issuecomment-2920870553 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 30 May 2025 00:20:19 UTC