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 plaintext ingress for HTTP01 challenges #698

Open
wasaga opened this issue Jul 19, 2023 · 0 comments
Open

support plaintext ingress for HTTP01 challenges #698

wasaga opened this issue Jul 19, 2023 · 0 comments

Comments

@wasaga
Copy link
Collaborator

wasaga commented Jul 19, 2023

Currently, we automatically redirect from port 80 to 443. That causes HTTP01 cert-manager challenges to fail if client CA is configured.

This is unfortunately non trivial to change, as all routes are configured in listener on port 443, while port 80 is doing just redirects.


unfortunately there's no way to disable client cert request just for the HTTP01 challenges as this is configured per port (443) and as such, HTTP01 challenges are fundamentally incompatible with mTLS. You have to use a different cert-manager Issuer challenge type, such as DNS.

Wouldn't it be possible to disable the https redirect on port 80 for the ACME challenge routes? That way we circumvent the problem entirely.

EDIT: Background info: Let's Encrypt verifies the challenges using plaintext requests but follows redirects.

Originally posted by @andsens in #697 (comment)

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