-
Notifications
You must be signed in to change notification settings - Fork 339
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
Why the intermediate CA certificates are not allowed in "provided" CA? #759
Comments
Envoy has this pretty old issue, which apparently is still relevant: envoyproxy/envoy#1220. I think it gives a good explanation, especially the last couple of comments. Then there was this user sharing their experience: envoyproxy/envoy#2675 I am sure there is more info around the internet. Does that help you with your question? |
That is very helpful for me. Thank you. |
Revisit intermediate CA support |
+1 to this issue |
Summary
Why the intermediate CA certificates are not allowed in "provided" CA?
https://kuma.io/docs/0.5.0/policies/mutual-tls/#usage-of-provided-ca
I found a comment like
Envoy constraint
in the code and I want to know more about it.https://github.com/Kong/kuma/blob/0.5.0/pkg/plugins/ca/provided/ca_cert_validator.go#L33-L35
The text was updated successfully, but these errors were encountered: