W3C home > Mailing lists > Public > public-webauthn@w3.org > April 2019

Re: [webauthn] How to get supported client extension (#1199)

From: Adam Langley via GitHub <sysbot+gh@w3.org>
Date: Thu, 18 Apr 2019 22:20:07 +0000
To: public-webauthn@w3.org
Message-ID: <issue_comment.created-484708567-1555626006-sysbot+gh@w3.org>
> For example, RP does not want to make caBLE authentication flow when the client does not support it although caBLE registration was done before with another client.

That's a concrete use case, but there's already enough places for the RP to enter this information for the platform to make a smart choice&mdash;i.e. the per-credential transports. If the platform finds that it just has a &ldquo;cable&rdquo; credential and doesn't support that transport it can display appropriate UI.

GitHub Notification of comment by agl
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1199#issuecomment-484708567 using your GitHub account
Received on Thursday, 18 April 2019 22:20:09 UTC

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