Deprecate the [server] ssl_ca_certificate setting, replacing with a new CA path setting
We currently have a setting in the [server] section of server.conf called ssl_ca_certificate. It must be a path to a specific CA certificate that is used for consumer yum repo files to validate that the Yum repository's SSL certificate is trusted.
Unfortunately there is also a setting called ca_cert, which is the certificate that Pulp uses to sign client certificates for authentication. These settings have little to do with one another yet have a meaning conflict in their names.
This should be removed. Instead we should have a consumer bool setting (i.e., not in server.conf) that allows the user to specify whether Yum should validate the server's signature with an authority pack. Additionally, a setting for a path to a directory containing certificates should be created so the user can provide their own certificate packs if they wish.
+ This bug was cloned from Bugzilla Bug #1123509 +
#1 Updated by rbarlow over 5 years ago
I think this might be important to do with 3.0. This setting cannot be used in a safe way, because it requires the consumer machine to have already registered and to have bound a repo before it can take any effect. This means that the consumer machines must already have trust on Pulp's CA certificate since they cannot safely use pulp-consumer without it. If the consumer machines already have trust on Pulp's CA, this setting isn't useful.
This setting also has a lot of potential for confusion, since it has such a general name and since its name is extremely similar to the cacert setting.
I'll untriage it so its priority and target release can be reconsidered. I've also removed the FutureFeature and RFE tags since this isn't really a feature but is truly a defect.
+ This comment was cloned from Bugzilla #1123509 comment 1 +
#10 Updated by bmbouter over 1 year ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Please register to edit this issue