W3C home > Mailing lists > Public > public-webauthn@w3.org > September 2020

Re: [webauthn] New platform authenticators are making discoverable credentials regardless of residentKey=false passed to Create() (#1457)

From: Arian van Putten via GitHub <sysbot+gh@w3.org>
Date: Tue, 15 Sep 2020 13:06:20 +0000
To: public-webauthn@w3.org
Message-ID: <issue_comment.created-692701186-1600175179-sysbot+gh@w3.org>
Would it be possible to let chrome for android throw an exception when `requireResidentKey = true` is set in a more short term though?  Currently I need to special case Chrome for Android by user agent matching as it seems to be the only one that doesn't conform to the L1 specification in this specific scenario. And that sounds more like a bug than a missing feature to me... Though I might be interpreting the spec too strictly. 

GitHub Notification of comment by arianvp
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1457#issuecomment-692701186 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 September 2020 13:06:22 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:41 UTC