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

Getting full chain in certificate #70

Open
alen-z opened this issue Aug 30, 2022 · 2 comments
Open

Getting full chain in certificate #70

alen-z opened this issue Aug 30, 2022 · 2 comments

Comments

@alen-z
Copy link

alen-z commented Aug 30, 2022

Hi,

do you think if it would make sense to offer a CRD flag to include full chain in auto-created certificate?

I noticed issues by serving created certificates to clients: curl: (60) SSL certificate problem: unable to get local issuer certificate. I guess because there is no full chain included.

Cheers!

Edit: If those are certificates used only to work behind CF proxies, then I probably missed the point. We are trying to use them for internal networking, not going over CF. Domains are, of course, managed in CF. Well, I think I've missed this: "You'll be able to use this certificate on servers proxied behind Cloudflare." — CF blog.

@terinjokes
Copy link
Contributor

Yes, they're intended only for services proxied by Cloudflare. The feature request is still valid: the issuer doesn't set ca.pem in the secret. There's no API to fetch the current Origin CA certificate, and I'm hesitant to hard code it.

@alen-z
Copy link
Author

alen-z commented Sep 4, 2022

Maybe no API, but there are 2 static endpoints that might serve as source of Origin CA.

I believe using a flag to include Origin CA would be nice. This is because Cloudflare can work without it and reliability of methods to get latest CA may vary.

Maybe few methods of getting Origin CA to think about:

  • Use embedded: For air gap environments. You need to maintain the embedded values. Even though 2029 (expiration date) is far away, it might still be an issue for cluster operators and you to make sure proper CA is used all the time.
  • Fetch latest: Use previously mentioned endpoints to fetch latest CA. Endpoints should be reliable. Does not work in air gap environments and in aggressive egress network policy setups. No maintenance from your side. Could fit majority of use cases.
  • Use custom: Allow cloud operators to include latest CA manually (or automate process of getting CA on their side).

I think having all of this options would allow cloud operators to choose the one that properly suits their needs.

How would you implement, would one method auto fall back to another and how it should be configured in CRD, I'll leave up to you :) I can share few thoughts if discussion starts going in implementation details direction.

Appreciate the interest in topic. Not to mention how awesome it'd be if Cloudflare was similar to Let's Encrypt — having certificates issued and being recognized by majority of clients because of embedded CA.

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

2 participants