Bug 1353441
| Summary: | Docs: replace /ca.crt with "/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yedidyah Bar David <didi> |
| Component: | Documentation | Assignee: | Julie <juwu> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | rhev-docs <rhev-docs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0.0 | CC: | cfergeau, didi, gklein, juwu, lsurette, rbalakri, srevivo, ykaul, ylavi |
| Target Milestone: | ovirt-4.0.3 | ||
| Target Release: | 4.0.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Release Note | |
| Doc Text: |
Previously, the Manager's CA certificate could be downloaded from: http://[engine-fqdn]/ca.crt. With this update, the URL to download the CA certificate has changed to: http://[engine-fqdn]/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA. Existing clients that use the old URL must be updated to use the new one.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-09 01:45:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1360991 | ||
|
Description
Yedidyah Bar David
2016-07-07 05:53:12 UTC
*** Bug 1362617 has been marked as a duplicate of this bug. *** Don't we break backwards compatibility this way? Don't we expect older clients to continue try and successfully retrieve the certificate from the old location? (In reply to Yaniv Kaul from comment #4) > Don't we break backwards compatibility this way? Don't we expect older > clients to continue try and successfully retrieve the certificate from the > old location? Example - https://github.com/GNOME/libgovirt/blob/f70802a769baa8113f26ba9287e453b9209d56f5/govirt/ovirt-proxy.c#L55 (In reply to Yaniv Kaul from comment #5) > (In reply to Yaniv Kaul from comment #4) > > Don't we break backwards compatibility this way? Don't we expect older > > clients to continue try and successfully retrieve the certificate from the > > old location? That's a good question, but too late... > > Example - > https://github.com/GNOME/libgovirt/blob/ > f70802a769baa8113f26ba9287e453b9209d56f5/govirt/ovirt-proxy.c#L55 It's already affected - 4.0 was released several months ago. Another question to ask is if we tried hard enough to inform users/3rd-parties about this. No idea about this. The ones that already contacted us and fixed their clients did this, AFAIK, only when they saw they are broken, when trying 4.0 or a beta. |