This repository has been archived by the owner on Sep 15, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 22
Implement impersonate user in Helm Broker #67
Labels
area/service-management
Issues or PRs related to service management
wontfix
This will not be worked on
Milestone
Comments
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to the lack of recent activity. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to the lack of recent activity. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area/service-management
Issues or PRs related to service management
wontfix
This will not be worked on
Description
The whole idea is already refined in the proposal
Consider going through the auth proxy instead of doing user validation in Helm Broker. In our flow, the user identity is always required, so we need to be sure that it is always present.
AC:
The text was updated successfully, but these errors were encountered: