JWT Support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
In order to facilitate authentication and authorization using the same mechanisms which are used in other parts of our ecosystem, it would be great to add JWT support to linkerd. Here are some use cases:
1. Linkerd is able to accept and verify a JWT with keys from an arbitrary endpoint.
2. Linkerd is able to parse claims in a JWT and drop inbound connections which don't have certain claims.
3. Linkerd is able to pass the parsed & verified JWT along in a header for use in the application it is proxying.
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
No files, tests, or entry points are named. Begin by reviewing Linkerd's existing authentication and authorization paths, then define the scope for key retrieval, claim enforcement, and verified-JWT header propagation; done would require an agreed design and coverage for all three use cases.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100