Description of problem: While doing lab in Summit we regenerated the SSL Certs using rhn-ssl-tool and inserted them into the DB using the rhn-ssl-dbstore. I noticed that the new RHN-ORG-TRUSTED-SSL-CERT was only placed into Org 1, the cert was NOT added into other ORGs. We need to fix rhn-ssl-dbstore. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
IMO, the SSL Certificate is a Satellite level entity. We should change the datamodel to use a single certificate across *all* orgs on the satellite vs storing on a per org basis. -Todd
does this require a db-query to check? guess I'm looking for a testplan
Test Plan: * Setup a multi org satellite with couple of orgs. * make note of the ssl cert on the ui for all the orgs(should be the default one) * Now create your own cert * upload your cert with rhn-ssl-dbstore command. * now check back the cert for each org in the ui, it should reflect the new cert you uploaded in all the sub orgs.
k.. the cert was distributed to org=0 and two other orgs.. Public CA SSL certificate: /tmp/RHN-ORG-TRUSTED-SSL-CERT Database connection string: rhnsat/rhnsat@rhnsat [root@rlx-3-06 tmp]# less RHN-ORG-TRUSTED-SSL-CERT [root@rlx-3-06 tmp]# checked in webui systems/kickstart/gpg verified
validated
5.1.1 Satellite is now GA, bugs Closed for Current Release.