- From: Firstyear via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 May 2023 03:34:20 +0000
- To: public-webauthn@w3.org
> > Why not leveraging [authenticatorSelection](https://w3c.github.io/webauthn/#dictionary-authenticatorSelection) with authenticatorAttachment? > > Adding a new attachment would break existing user-agents. We could work around that with a feature-detection system but then we would still have the issue that authenticatorSelection only exists for create(). For discoverable get() there wouldn't be any corresponding mechanism. That would be a bug in that user-agent then, because any rp could fill them with unknown values today and cause issues. So I think authenticator attachment still seems like a better place for this. It's a bit of a concern that we are adding a third area for authentication selection, given that we already have transports and attachament selectors. So I think the bigger risk is for there to be inconsistent and odd behaviours if you specify multiple or combinations of these parameters. -- GitHub Notification of comment by Firstyear Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1884#issuecomment-1532419198 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 May 2023 03:34:22 UTC