- From: Matthew Miller via GitHub <sysbot+gh@w3.org>
- Date: Sun, 11 Jun 2023 23:59:24 +0000
- To: public-webauthn@w3.org
> @MasterKale it seems like your use case is for and ideintier first flow where you know what transports are set on the available credentialID. In that case, are you looking for the available transports as what you really want? That's correct, we identify the user before populating `allowCredentials` with their credentials. I could see something that returns "available transports" as useful in troubleshooting user issues after failed authentication attempts. But if WebAuthn raises a "user clicked cancel" error for an allowCredentials with `["internal", "hybrid"]` in it because we were told both were possible but `"internal"` didn't match and the user gave up, we'd not really be better or worse off than we are now. Which might make "available transports" less useful than they first seem... I'll take that back to my team and think it through. Maybe I can more coherently communicate my higher-level request in a new issue because I think it's probably just making PR feedback here too noisy. -- GitHub Notification of comment by MasterKale Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1901#issuecomment-1586383907 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 11 June 2023 23:59:26 UTC