Skip to content

Commit c0f764f

Browse files
authored
Merge pull request #530 from gerases/add-docs-on-ca-expiration-fixups
Style fixes
2 parents 927daab + fd92e40 commit c0f764f

1 file changed

Lines changed: 5 additions & 9 deletions

File tree

_docs/extending-expired-ca-cert.md

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ date: 2025-08-06
55
summary: How to extend the expiration date of the Puppet CA certificate
66
---
77

8-
## Using an OpenBolt Module
8+
## Using an OpenBolt module
99

1010
If you're using OpenBolt in your environment, there's a [ca_extend](https://github.com/puppetlabs/ca_extend) module designed for this task. Follow the module’s documentation to perform the extension in a supported and automated way.
1111

12-
## Manual Process
12+
## Manual process
1313

1414
The [ca_extend repository](https://github.com/puppetlabs/ca_extend) also includes a standalone [extend.sh](https://github.com/puppetlabs/ca_extend/blob/main/files/extend.sh) script that can be run manually to generate a new CA certificate with an extended expiration date.
1515

@@ -24,18 +24,14 @@ The script performs the following steps:
2424

2525
The new file will be named using the format: `ca_crt-expires-<NEW_END_DATE>.pem`. This allows you to distinguish it from the currently active certificate without overwriting anything by default.
2626

27-
## Steps After Running the Script
27+
## Steps after running the script
2828

2929
1. Examine the end date of the new certificate by executing:
30-
3130
```
32-
openssl x509 -in <PATH_TO_NEW_KEY> -noout -noout -subject -issuer -enddate
31+
openssl x509 -in <PATH_TO_NEW_KEY> -noout -subject -issuer -enddate
3332
```
34-
3533
Confirm the issuer matches your existing CA and that the expiration date is 15 years in the future.
36-
3734
2. Back up the current certificate and install the new one:
38-
3935
```
4036
# Assuming the directory where the CA is stored is /etc/puppetlabs/puppet/ssl/ca
4137
mv /etc/puppetlabs/puppet/ssl/ca/ca_crt.pem /etc/puppetlabs/puppet/ssl/ca/ca_crt.pem.bak.$(date +%F)
@@ -65,7 +61,7 @@ A command similar to the above would need to be orchestrated across all of your
6561
## OpenVox agents on version 8 and newer
6662
Agents running Puppet 8+ will automatically fetch the updated CA certificate according to the [ca_refresh_interval](https://github.com/OpenVoxProject/openvox/blob/main/references/configuration.md#ca_refresh_interval) setting.
6763

68-
## Older Agents
64+
## Older agents
6965

7066
For older agents:
7167

0 commit comments

Comments
 (0)