deckhouse / deckhouse/deckhouse
[user-authn] Limit connectors available for DexAuthenticator / DexClient
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 162
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 653
Description
Preflight Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Use case. Why is this important?
For multitenant access, it may be required to see only specific options for specific applications to login with.
For example, there is a Dex in the cluster. There is Grafana, which can be accessed by infrastructure engineers using their GitLab. There is also a dev stand that can be accessed by managers that do not have GitLab accounts but they have a corporate OIDC access.
Proposed Solution
Patch Dex to filter connectors available based on the client.
Additional Information
No response
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
Begin by locating the DexAuthenticator and DexClient implementations and the connector configuration or handling they use. The issue's done condition is client-specific connector visibility, but it does not identify files, tests, or the filtering contract; clarify those before implementation.
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