Skip to content
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

SPIKE: Passkey UX in browser extensions #1762

Open
aristidesstaffieri opened this issue Jan 6, 2025 · 0 comments
Open

SPIKE: Passkey UX in browser extensions #1762

aristidesstaffieri opened this issue Jan 6, 2025 · 0 comments

Comments

@aristidesstaffieri
Copy link
Contributor

aristidesstaffieri commented Jan 6, 2025

Passkey implementations in browser extensions are still fairly new and may be limited in scope.
We need to understand how passkeys work in the context of a browser extension.

Can you achieve a similar UX as a website given the "extension domain" is not a real domain(some browsers set the relying party ID as this domain behind the scenes)?
Which browsers support passkeys in extensions and are the implementations capable of the same UX?
Are there any other constraints?

Related links:
Relying Parties
https://github.com/w3c/webauthn/issues/1158
https://issues.chromium.org/issues/41378082
https://stackoverflow.com/questions/77485521/can-a-chrome-extension-directly-initiate-the-chrome-webauthn-passkey-dialogu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant