Skip to content

Conversation

DSpeichert
Copy link
Contributor

Fixes #51

Solution by @jonasvanderhaegen

This aligns the selection criteria with documentation to allow the passkey to be "discovered".

Per https://simplewebauthn.dev/docs/advanced/passkeys#server, these must be set:

// "Discoverable credentials" used to be called "resident keys". The
// old name persists in the options passed to `navigator.credentials.create()`.
residentKey: 'required',
userVerification: 'preferred',

@freekmurze
Copy link
Member

The tests are failing. Could you look at that?

Fixes spatie#51

This aligns the selection criteria with documentation to allow the passkey to be "discovered".

Per https://simplewebauthn.dev/docs/advanced/passkeys#server, these must be set:

    // "Discoverable credentials" used to be called "resident keys". The
    // old name persists in the options passed to `navigator.credentials.create()`.
    residentKey: 'required',
    userVerification: 'preferred',
@DSpeichert
Copy link
Contributor Author

The tests are failing. Could you look at that?

Should be working now :)

@DSpeichert
Copy link
Contributor Author

Very weird that the order of keys is different for me when running the test locally, it should be happy now.

@DSpeichert
Copy link
Contributor Author

Turns out the GitHub editor also likes to auto-add EOLs. I really hope the tests pass now, please approve workflow @freekmurze.

@freekmurze freekmurze merged commit 3daecdd into spatie:main Sep 25, 2025
7 checks passed
@freekmurze
Copy link
Member

Thank you!

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

Successfully merging this pull request may close these issues.

[Bug]: After registering passkey on Bitwarden password manager, with authentication prompt there're no passkeys
2 participants