- From: Firstyear via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Nov 2022 00:27:07 +0000
- To: public-webauthn@w3.org
Correct, there is no one size fits all here, but currently for *consumers* you can not prescribe or assume what authenticators will be used, and you also can't prescribe the ability or subject matter expertise of a user. Currently, even if you set rk=discouraged, you will get the "full features" that users can enjoy as you state when users use their platform authenticators as these will always force rk=true internally, and you lose nothing. And you also get working support for users to use their other non-platform bound authenticators. So what is the problem? -- GitHub Notification of comment by Firstyear Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1822#issuecomment-1311074815 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 November 2022 00:27:09 UTC