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

Merge Passkey and U2F tokens #7882

Open
livio-a opened this issue May 1, 2024 · 1 comment
Open

Merge Passkey and U2F tokens #7882

livio-a opened this issue May 1, 2024 · 1 comment
Assignees

Comments

@livio-a
Copy link
Member

livio-a commented May 1, 2024

We currently have two separate pools for passkey and U2F tokens. Since most clients can only handle a single token for an WebAuthN OP, this led to problems when using the same device for Passkey and U2F, where the second one wins over the first.

The session API already has a single webauthn challenge, where depending on the user_verification flag, possible tokens / devices are allowed.

We should move the tokens / devices into a single list so that a device can only be used once.

@muhlemmer
Copy link
Contributor

Also take #4758 into account when redesigning the storage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🧐 Investigating
Development

No branches or pull requests

2 participants