Forward Authorization-Extras header to Codec Server
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 431
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 71
Description
Is your feature request related to a problem? Please describe.
In our Temporal setup we use OIDC with Azure as provider for authentication, the roles and metadata of the users for the application are present in the "Authorization-Extras" header which the web forwards to the frontend for authorization. But the web does not forward this header to the codec server, only the "Authorization" header.
We use the roles to restrict access to users to only their registered namespaces.
Describe the solution you'd like
We would like the "Authorization-Extras" header to be forwarded as well, to the codec server when "Pass the user access token with your endpoint." option is selected.
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 at the web request path to the codec server when the “Pass the user access token with your endpoint.” option is selected. Verify how the Authorization header is forwarded, then ensure Authorization-Extras follows the same path and confirm the codec server receives it in that mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100