Use the same Let's Encrypt credentials on all machines #519

New Issue

raucao · 2023-10-22T13:42:22Z

raucao commented

2023-10-22 13:42:22 +00:00

I added CAA records for the various accounts currently in use, but it's too messy this way (and I'm sure I didn't add all of them). It should just be one trusted account that is allowed to issue certificates and that can be configured and updated via Chef.

I added[ CAA records](https://letsencrypt.org/docs/caa/) for the various accounts currently in use, but it's too messy this way (and I'm sure I didn't add all of them). It should just be one trusted account that is allowed to issue certificates and that can be configured and updated via Chef.

raucao added the

security

enhancement

labels 2023-10-22 13:42:22 +00:00

raucao commented

2023-12-02 12:00:24 +00:00

Note: Since we have switched the public web proxies to OpenResty, we could now also use auto-ssl instead of Certbot for the nginx sites there.

Note: Since we have switched the public web proxies to OpenResty, we could now also use [auto-ssl](https://github.com/auto-ssl/lua-resty-auto-ssl) instead of Certbot for the nginx sites there.

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#519