tink-crypto / tink-crypto/tink-java
Add support for more JWT headers
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 305
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? If so, provide a description of the problem.
I am currently working on migrating an internal library handling JWT in Java from nimbus-jose to Tink. We are using Tink keysets and primitives, but some of our partners require certain headers (cty, crit, x5c, x5t256, b64, as well as custom ones).
What sort of feature would you like to see?
I know Tink only supports typ, alg and kid, but is there a chance that more will be added in the future? If not, do you see an alternative way to use Tink primitives for JWT signatures given that these headers are required?
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
The issue names no files, tests, or entry points; start by locating Tink's Java JWT support and its current handling of typ, alg, and kid. Clarify which additional headers and API behavior are required, then define completion as support for the agreed headers or a documented alternative for signing with Tink primitives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100