-
Notifications
You must be signed in to change notification settings - Fork 11
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
Pass a list of allowed origins instead of a single origin #184
Conversation
Android and iOS also support WebAuthn just like browsers. The apps will use their AppStore/PlayStore AppID as the origin. This means we need to allow a list of origins instead of a single origin. Apple uses https://developer.apple.com/documentation/xcode/supporting-associated-domains to link the app origin to the RpId Google uses an assetlinks.json file: https://developers.google.com/identity/fido/android/native-apps#interoperability_with_your_website
Multiple origins looks like a Webauthn 3 (which is still a draft) specific notion, see https://www.w3.org/TR/webauthn-3/#sctn-validating-origin, this doesn't seem to be documented in Webauthn 2. This library currently only implements Webauthn 2, but this seems very benign, and since it's already used in practice, it sounds fine to add. Please add some comments to the code/docs to explain this context. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this is looking good! Made a bunch of suggestions for more consistency, especially regarding imports (there were some duplicate qualified imports of NonEmpty
too), but also some other minor things
Would also be neat to have a test with two origins ;) |
Co-authored-by: Silvan Mosberger <[email protected]>
I added some quickcheck properties now. Hope this suffices? :D PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good to me!
Android and iOS also support WebAuthn just like browsers.
The apps will use their AppStore/PlayStore AppID as the origin. This means we need to allow a list of origins instead of a single origin.
Apple uses https://developer.apple.com/documentation/xcode/supporting-associated-domains to link the app origin to the RpId
Google uses an assetlinks.json file:
https://developers.google.com/identity/fido/android/native-apps#interoperability_with_your_website