-
Notifications
You must be signed in to change notification settings - Fork 10
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
[low] check TLS cert secret actually matches the host #60
Labels
enhancement
New feature or request
Comments
wasaga
changed the title
check TLS cert secret actually matches the host
[low] check TLS cert secret actually matches the host
Oct 27, 2021
Do we have more details about what the issue is here? What's the configuration that can lead to the problem? |
calebdoxsey
added
blocked
PR/ISSUE is blocked by third party
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
labels
Jan 19, 2022
travisgroth
removed
blocked
PR/ISSUE is blocked by third party
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
labels
Jan 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
apparently
cert-manager
would not complain if you specify an ingress and definehost
that does not match the contents of the referenced secret.pomerium would then bind this route to the first cert it has in the chain.
Describe the solution you'd like
we probably should perform this check and consider it an invalid configuration.
The text was updated successfully, but these errors were encountered: