refactor: Use webauthn library native JSON encodings #579
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.
What is the purpose of this change?
Instead of using handwritten
play-json
encodings this change makes use of the Json annotations that have already been attached to the models of thewebauthn4j
library.What is the value of this change and how do we measure success?
This is to avoid having to remember to update Json encodings whenever we use an extra field. It also gives us more consistency in that we're now using the
webauthn4j
library to encode and to decode Json in web requests and responses.Any additional notes?
This is to pave the way for adding
excludeCredentials
argument to ourPublicKeyCredentialCreationOptions
, which in turn will stop the possibility of registering duplicate and therefore redundant passkeys.