VEuPathDB / VEuPathDB/OAuth2Server
Upgrade JJWT to more recent version
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
JJWT is now at 0.12.5 (up from 0.11.5, which we upgraded to during bearer token enhancements). It does offer some new features which could cut down on our custom code, but has a moderately different API and so upgrading is a bit of a project to figure out the new methods/procedures for doing what we need to do, esp regarding signatures and signature algorithms. Should probably do this at some point (it may be beyond 0.12.5 by then), but not an emergency.
https://github.com/jwtk/jjwt
https://mvnrepository.com/artifact/io.jsonwebtoken/jjwt-api
Contributor guide
No contributing guide indexed for this repository
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 locating the JJWT dependency declaration and the current bearer-token signing and signature-algorithm code. Compare those usages with the JJWT 0.12.5 API, then verify that the OAuth2 server still builds and preserves its existing token-signing behavior after the dependency upgrade.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100