Support Authentication Token in OpenAPI
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 431
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 71
Description
Hi Temporal Team, I am Bart from LinkedIn. My Temporal and Temporal-UI are all running. Temporal-UI is working with SSO authentication enabled, and the JWT token was successfully sent to Temporal server’s authorizer plugin. However, the APIs over the UI Swagger (OpenAPI) page doesn’t work. The APIs always reports 401 (Unauthorized) error. Executing the API doesn’t look like it triggering the Temporal server’s authorizer plugin at all. 401 looks like it gets returned from Temporal-UI directly. Is there any way for me for the swagger page to fix the 401 error? Wish you can prioritize this issue soon. Otherwise Can you give us the pointers how to modify the code to support the feature? My team may try to change it. Thank you!
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
No file, test, or entry point is named. Start by tracing the Temporal-UI Swagger/OpenAPI request path and its authentication handling; done means Swagger API calls forward the JWT to Temporal server authorization instead of returning a direct 401 from Temporal-UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, typescript
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100