New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supported features detection from the browser #1202
Comments
Which specific features do you need to detect? |
Core features that we want to detect are followings:
As @akshayku mentioned, for RP perspective, we need to get such information for making concrete use cases. |
@akshayku and I have been discussing this on our side as well. We've been thinking of something along the lines of the following, accounting for the items mentioned above as well as some additional ones: interface supportedCapabilities { partial interface PublicKeyCredential { Will open a PR as well. |
Removed pr-open label since #1219 was closed. |
closing this since we closed the PR |
This issue is related to the #1199 and this is more broader cases.
We, LINE, are trying to leverage WebAuthn for our login flow and suffering some issues handling different browsers/platforms.
RPs supporting WebAuthn already may have some logics to enable or disable supporting WebAuthn by looking at user agent information.
For real word implementation, it is very hard for us to detect such supported or not-supported features from UA.
It is better to have some APIs to provide supported features for RP to easily leverage the features.
The text was updated successfully, but these errors were encountered: