vimalloc / vimalloc/flask-jwt-extended
Setting 'kid' claim as part of encode_key_loader
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 253
- PR merge metrics
- No merged PRs in 30d
Description
Firstly thanks for maintaining the library!
I'm using encode_key_loader to specify keys for different types of JWTs in my application. I realized that we cannot set the kid claim in encode_key_loader or conversely read the kid within encode_key_loader to determine which key to use. Was this a purposeful restriction, or are you open enabling this?
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
The issue centers on encode_key_loader; start by tracing how this callback is used when selecting keys for JWTs. Clarify whether it must read the kid claim, set it, or support both; done means the requested kid behavior works when encoding and selecting keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100