Avoid requesting an unnecessary attestation statement when creating a webauthn credential #16252
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The attestation option in PublicKeyCredentialCreationOptions is a parameter that controls whether to request attestation statement from the security key. Currently, Spring Security Passkeys requests attestation statement by specifiy
direct
value toattestation
option, but Spring Security Passkeys doesn't implement attestation statement verification[1]. Therefore, the requested attestation statement is not used at all.Specifying
direct
to request attestation may trigger browsers to display additional privacy related dialog to users, so it is best to avoid specifyingdirect
unnecessarily.[1] Spring Security Passkeys uses WebAuthnManager.createNonStrictWebAuthnManager() to setup a
WebAuthnManager
instance configured not to verify attestation statements.