Serve TLS-Challenge certificate in first #3605
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
The PR modifies the order in the
getCertificate
implementations if ACME certificates can be generated tahnks toTLS-ALPN
challenge.Motivation
Users can have a generic wildcard self-signed certificate and want to serve a Let's Encrypt certificate only for few specific subdomains.
In the original order, it was not possible to generate a ACME certificate, thanks to the
TLS-ALPN
challenge, for a domain which is already cheked by a provided wildcard domain certificate.The new order checks if a temporary ACME certificate is enable for the requested domain before to check the others certifcates.
More
Additional Notes
Rename toml file in ACME E2E tests to be homogeneouse.