- From: Adam Langley via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Apr 2021 17:48:58 +0000
- To: public-webauthn@w3.org
> I'm interested to understand how this discussion can lead to changes in the spec (who has authority on it) and how we can all collaborate to extend the support of WebAuthn. This is the group that does spec changes, so you're in the right place. I'm guessing from your wording “interoperability issues with other implementations of FIDO2 on other platforms like Android / iOS” that you're considering the extension to be an app, rather than the classic use of an extension to tweak other sites. Thus you want the app to have a consistent RP identity across platforms so that users can sign into it across them? If that's the case then I think an extension is not quite the right model. If you want a consistent RP identity then (absent large changes) that's a domain. If you use a PWA rather than an extension then you can still work offline etc, but you can register and assert credentials using a domain name. On Android, a native app can use Android's WebAuthn APIs with that domain as the RP ID if it sets up asset links ([docs](https://developers.google.com/identity/fido/android/native-apps#interoperability_with_your_website)). iOS doesn't currently offer a WebAuthn API to native apps that I'm aware of. -- GitHub Notification of comment by agl Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1372#issuecomment-812638236 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 April 2021 17:48:59 UTC