You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow users to provide their own server certificates via
--certificate-server-certificate, --certificate-server-key, and
--certificate-server-ca-certificate flags on foremanctl deploy.
Custom certificates are copied into the canonical /root/certificates/
structure, while client certificates and localhost certificates continue
to be managed by the internal CA.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Install dependencies (`python3-cryptography`) and create directory layout under `certificates_ca_directory`
122
161
- Generate RSA private key (size from `certificates_algorithm_size`, default 4096)
@@ -129,21 +168,40 @@ src/roles/certificates/
129
168
130
169
Generation uses **`community.crypto`** (keys, CSRs, X.509) and **`python3-cryptography`**.
131
170
171
+
For `certificate_source: custom_server`:
172
+
173
+
1.**CA Generation**: Generate self-signed internal CA certificate and key with 20-year validity
174
+
2.**Custom Server Certificates**: Copy the custom server cert, key, and CA bundle from user-provided paths to `/root/certificates/` (only when certificate paths are provided)
175
+
3.**Host Certificate Issuance**: Generate client certificate and localhost certificate signed by the internal CA (server cert for FQDN is skipped)
176
+
177
+
For `certificate_source: installer`:
178
+
179
+
- Uses existing certificates from `/root/ssl-build/` generated by foreman-installer
180
+
- No certificate generation performed; files must already exist
181
+
132
182
#### Variable System
133
183
134
184
Certificate paths are defined in source-specific variable files:
0 commit comments