- From: Firstyear via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Nov 2022 00:01:47 +0000
- To: public-webauthn@w3.org
> I'm thinking that this is up to the user's choice not the RP's preference. So, if the RP tries to create RK and the space is limited to create new credential, browsers and platforms might handle such cases by presenting and eventually prompting credential management UI to the user or guiding the user to use another authenticator. If the user's authenticator has no enough room to create a new RK and the user is not willing to create the one by removing registered credential, the browser or platform might return an appropriate error indicating the insufficient space or something. I think the issue here is that not all users will have the knowledge to make an informed decesion about this problem. As a result, this would create user friction. So I think the distinction has to be "unlimited vs not" and the browser needs to automatically choose the correct rk status based on this property. I think we must not rely on user interaction to choose if rk should be true/false. -- GitHub Notification of comment by Firstyear Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1822#issuecomment-1311058113 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:01:48 UTC