Skip to content

Add cname support#304

Merged
evgeni merged 1 commit intotheforeman:masterfrom
ehelms:add-cname-support
Mar 9, 2026
Merged

Add cname support#304
evgeni merged 1 commit intotheforeman:masterfrom
ehelms:add-cname-support

Conversation

@ehelms
Copy link
Member

@ehelms ehelms commented Nov 14, 2025

This includes #294

This aims to add cname support to the default set of certificates, which is functionality foreman-installer allowed.

@ehelms ehelms force-pushed the add-cname-support branch 2 times, most recently from ed3ede4 to 640e718 Compare December 5, 2025 16:51
@ehelms
Copy link
Member Author

ehelms commented Dec 5, 2025

Rebased

@ehelms ehelms force-pushed the add-cname-support branch from 640e718 to e3d2e24 Compare January 31, 2026 20:55
@ehelms ehelms force-pushed the add-cname-support branch from e3d2e24 to 841ee07 Compare March 5, 2026 21:43
-key "{{ certificates_ca_directory_keys }}/{{ certificates_hostname }}.key"
-subj "/CN={{ certificates_hostname }}"
-addext "subjectAltName = DNS:{{ certificates_hostname }}"
-addext "subjectAltName = DNS:{{ certificates_hostname }}{% for cname in certificates_cnames %},DNS:{{ cname }}{% endfor %}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

quite unrelated to this particular PR, I realized we do not regenerate the cert if any of its properties change. should we?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aye, tracking -- #401

@evgeni evgeni merged commit f7feb4c into theforeman:master Mar 9, 2026
11 checks passed
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 this pull request may close these issues.

2 participants