I referenced this site when initially looking into third party certificates with Spacewalk: http://www.marsdominion.com/2013/02/01/configuring-a-rhn-satellite-server-with-a-third-party-cert/
For my configuratoin (weighted load balancer for failover), I was able to simply append our company's Root CA cert to the end of the RHN-ORG-TRUSTED-SSL-CERT file and distribute it to clients. This requires that you have reverse DNS resolution on the VIP. Unless you are doing load balancing\failover, I'd recommend using the self signed certificate.. it's much easier and will probably save you a lot of headache with OSAD\Jabberd configuration. On Wed, Jul 23, 2014 at 4:55 AM, Alexander Dacre <[email protected]> wrote: > Hi, > > > > I’m looking for some guidance on using a non-self-signed certificate with > Spacewalk – the documentation I’ve found seems to be around recreating the > self-signed ones. > > > > There is also a question around benefits of using a non-self-signed cert. > My understanding is that it is used for front-end web and back-end > client/server communication. With this in mind, does it make sense to use > the self-signed certificate due to less management overhead? > > > > Thanks, > > Alex > > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
