- From: Firstyear via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Jul 2022 07:18:48 +0000
- To: public-webauthn@w3.org
This is probably something for the adoption group. Anyway, when you do discoverable, the client works out what credential to use. It fills that in (and can pop up with conditional UI stuff). Then in the authentication this contains the client ID which is a unique identifier. You can use that unique identifier to work out the account associated with that credential and then verify the public key. The idea of them is that the user doesn't need to enter a username at all, they just present their token/credential, and it identifies AND authenticates the user. If you need worked code examples, look at https://github.com/kanidm/webauthn-rs which is a really complete library. Alternately consider using an existing library. -- GitHub Notification of comment by Firstyear Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1764#issuecomment-1175868906 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 July 2022 07:18:50 UTC