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

Support connecting to endpoints using a SOCKS5/HTTP proxy #28667

Open
semekh opened this issue Oct 10, 2024 · 0 comments
Open

Support connecting to endpoints using a SOCKS5/HTTP proxy #28667

semekh opened this issue Oct 10, 2024 · 0 comments

Comments

@semekh
Copy link

semekh commented Oct 10, 2024

Is your feature request related to a problem? Please describe.
Vault needs to have network access to different components as secret engines. This might not be feasible when:

  1. The target is in a private network and does not have a public IP address
  2. The target is in a network where only outbound connections are allowedE
  3. One doesn't want to expose the target on a public network

Describe the solution you'd like
While providing direct network access might not be secure and maintainable, if Vault could connect to targets through a proxy server, the proxy server could do the heavy-lifting of routing, access control, audit, etc. Implementing the socks5/http proxy for handling TCP connections could be generic enough, so that the user could bring their own implementation of proxies.

Describe alternatives you've considered
The proxying could be performed through a transparent proxy mechanism, but that is less than ideal since it's all or nothing and less configurable.

Explain any additional use-cases

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants