Non-OIDC JWT Auth handling
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.
Currently, if Frontend JWT auth is configured as per Temporal Security Doc, the UI shows the following error in case of an invalid JWT token or if the JWT token is valid but the user has no permissions:
Describe the solution you'd like
I would like to be able to configure JWT token validation on the Web UI component and better handling of JWT errors from the frontend service.
Describe alternatives you've considered
N/A
Additional context
N/A
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 with the linked Temporal Security documentation, then trace how the Web UI configures frontend JWT authentication and receives JWT errors from the frontend service. Done means the UI can configure JWT validation and handles invalid tokens or valid tokens without permissions with clearer behavior than the current error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100