Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] - Refactor DEX Controller #798

Open
3 tasks
IvoGoman opened this issue Dec 11, 2024 · 0 comments
Open
3 tasks

[FEAT] - Refactor DEX Controller #798

IvoGoman opened this issue Dec 11, 2024 · 0 comments
Labels

Comments

@IvoGoman
Copy link
Contributor

Priority

(Medium) I'm annoyed but I'll live

User Story

No response

Description

The DexController is responsible for provisioning DEX resources (OAuth2Client, Connector) for each Organization.
Currently these resources are created in the greenhouse namespace and are thus not accessible for the Organization.
Furthermore, the OAuth2Clients do not specify a ClientSecret, which is required by the oauth2-proxy to be used for securing the services exposed via service-proxy.

Acceptance Criteria

  • DexController creates the Dex resources in the Organization's namespace
  • OAuth2Clients receive a generated client secret
  • ClientSecret for the OAuth2Client is saved in the organizations namespace <org>-dex-secrets

Reference Issues

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Sprint Backlog
Development

No branches or pull requests

1 participant