- From: Adam Langley via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Apr 2019 22:20:07 +0000
- To: public-webauthn@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—i.e. the per-credential transports. If the platform finds that it just has a “cable” 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