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

Why the intermediate CA certificates are not allowed in "provided" CA? #759

Closed
ryysud opened this issue May 22, 2020 · 4 comments · Fixed by #2575
Closed

Why the intermediate CA certificates are not allowed in "provided" CA? #759

ryysud opened this issue May 22, 2020 · 4 comments · Fixed by #2575

Comments

@ryysud
Copy link

ryysud commented May 22, 2020

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

@nickolaev
Copy link
Contributor

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?

@ryysud
Copy link
Author

ryysud commented Jul 20, 2020

That is very helpful for me. Thank you.

@jakubdyszkiewicz
Copy link
Contributor

Revisit intermediate CA support

@nikita15p
Copy link
Contributor

nikita15p commented Mar 15, 2021

+1 to this issue

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

Successfully merging a pull request may close this issue.

4 participants