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

Feature Request: Multiple SSL certificate support for HTTP endpoints #1104

Open
Thunderbottom opened this issue Oct 30, 2024 · 0 comments
Open

Comments

@Thunderbottom
Copy link

Currently, SSL for HTTP endpoints on warpgate only works in these two cases with externally mapped domains:

  1. The externally mapped domain (eg. git.domain.com) is on the same domain as warpgate (eg. warpgate.domain.com) and warpgate uses a wildcard certificate. Or in case where warpgate runs on a domain wg.domain.com and the services are git.wg.domain.com with a wildcard for *.wg.domain.com.
  2. Warpgate is running behind a load balancer, which handles SSL termination with multiple certificates.

We have a use case where we'd like to have multiple such SSL certificates handled by warpgate itself, instead of the load balancer for simpler deployments. This would allow us to run services on multiple domains (.net, .com, .io, etc) and put them behind warpgate. This is particularly useful in cases where there's multiple organizational domains, each for a particular group of users.

Let me know what you think of this.

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

No branches or pull requests

1 participant