Implement header authorization header auth for the dashboard
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
## Feature Request
Permit authentication in the dashboard based on authorisation header.
### What problem are you trying to solve?
Use central authentication mechanism (such as Keycloak) which give users full access to objects they are granted using RBACs.
### How should the problem be solved?
Implement Header authorisation token like in the kubernetes dashboard.
Then you can use dex or keycloak or any Oauth server to provide secure access
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 locating the dashboard authentication entry point and reviewing how the dashboard currently authenticates users. Compare the requested authorization-header token flow with the Kubernetes Dashboard approach and determine how Dex or Keycloak-issued tokens should grant RBAC-based access; done means the dashboard securely accepts and enforces that flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100