Bug 2079799 - issue the internal Certificate Authority for 20 years
Summary: issue the internal Certificate Authority for 20 years
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.5.0-1
: 4.5.0.7
Assignee: Michal Skrivanek
QA Contact: Petr Kubica
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-28 09:40 UTC by Michal Skrivanek
Modified: 2022-05-23 06:21 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.5.0.7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-23 06:21:25 UTC
oVirt Team: Infra
Embargoed:
sbonazzo: ovirt-4.5+
lsvaty: exception+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 319 0 None open issue internal CA for 20 years 2022-04-28 09:50:05 UTC
Github oVirt ovirt-engine pull 347 0 None open Backport CA and certificate fixes to 4.5.0.z 2022-05-09 14:12:03 UTC
Red Hat Issue Tracker RHV-45881 0 None None None 2022-04-28 10:49:14 UTC

Description Michal Skrivanek 2022-04-28 09:40:36 UTC 
Currently our internal CA is always issued for 10 years during the initial engine-setup. This carries over upgrades and on old enough installations we can get close to expiration. We don't have an easy way how to replace internal CA without complete downtime, and running over the expiration date leads to a complete cease of communication between all oVirt components.

20 years sounds slightly better
Comment 1 Michal Skrivanek 2022-04-28 09:45:41 UTC 
best to apply to QEMU CA as well. Not that VMs stick around running for such a long time, but just so we don't differ and don't have to renew at different times.
Comment 2 Petr Kubica 2022-05-13 08:40:52 UTC 
Verified in ovirt-engine-4.5.0.7-0.9.el8ev.noarch

# openssl x509 -text -in ca.pem
....
        Validity
            Not Before: May 11 13:54:00 2022 GMT
            Not After : May  7 13:54:00 2042 GMT
....
Note You need to log in before you can comment on or make changes to this bug.