temporalio / temporalio/temporal
Support nested `PermissionsClaimName`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
Some JWT providers use nested claims format, like:
{
"traits": {
"temporal": [
"one",
"two",
"three"
]
}
}
Configuring PermissionsClaimName to traits.temporal would allow to use them without needing to write CustomClaimsMapper.
Describe the solution you'd like
Ability to specify JSONPath for PermissionsClaimName.
Describe alternatives you've considered
Creating custom ClaimsMapper as per https://docs.temporal.io/self-hosted-guide/security#authorization
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 tracing how PermissionsClaimName is read and how the documented CustomClaimsMapper authorization path handles claims. Verify that configuring traits.temporal resolves the nested values without a custom mapper, and add coverage for the nested JSON claim format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100