spring-projects / spring-projects/spring-security
Add serialize/deserialize `PublicKeyCredentialRequestOptions` support with `ObjectMapper`
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Spring Security should add support for serialize/deserialize PublicKeyCredentialRequestOptions with ObjectMapper so it is easier to persist with Spring Session.
NOTE: WebauthnJackson2Module is used for reading/writing to the HTTP Response which includes untrusted inputs. This means that it cannot enable default-typing otherwise it could create deserialization vulnerabilities.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the WebauthnJackson2Module and its ObjectMapper integration, then trace how PublicKeyCredentialRequestOptions is handled for HTTP responses and Spring Session persistence. Done means the type can be serialized and deserialized for persistence without enabling default typing, preserving the security constraint for untrusted HTTP inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100