On Thu, Feb 16, 2012 at 6:47 PM, Jeremy Davis jdavis4...@gmail.com wrote:
Yes, that is the correct cert. You also need to make sure you download that
cert to the client and change the /etc/sysconfig/rhn/osad.conf to point to
that downloaded cert from the proxy server.
Ok, so here are the
Yes the CN needs to be that of the proxy server that is listed in
/etc/sysconfig/rhn/up2date file. This Cert should be at location
http://spacewalkproxy01.dc.company.com/pub/RHN-ORG-TRUSTED-SSL-CERT
On 02/17/2012 09:18 AM, Sean Carolan wrote:
On Thu, Feb 16, 2012 at 6:47 PM, Jeremy
So I wonder why the certificate is being generated with the wrong
name? It contains the name of the upstream Spacewalk server, instead
of it's own hostname. Is there something wrong with the data in my
answers file?
Incidentally I noticed that jabber seems to use a different SSL
certificate; in
On Thu, Feb 16, 2012 at 4:53 PM, Jeremy Davis jdavis4...@gmail.com wrote:
If a server is connecting to a Spacewalk Proxy server you will need to use
the SSL Cert that was generated for that proxy server. This Cert will be in
the same location as the app server but on the proxy server.
How is
server.pem and RHN-ORG-TRUSTED-SSL-CERT are two different things.
server.pem is for jabberd. the CN in server.pem should be your spacewalk
proxy's fqdn. RHN-ORG-TRUSTED-SSL-CERT should be identical to your
non-proxied clients' (at least it is in our environment). Double check
that the id/id
On Fri, Feb 17, 2012 at 2:11 PM, Wojtak, Greg (Superfly)
gregwoj...@quickenloans.com wrote:
server.pem and RHN-ORG-TRUSTED-SSL-CERT are two different things.
server.pem is for jabberd. the CN in server.pem should be your spacewalk
proxy's fqdn. RHN-ORG-TRUSTED-SSL-CERT should be identical to
Maybe one of you have already solved this in the past. We have a
master Spacewalk server which is working just fine. All clients are
able to contact the jabber server and receive push updates, etc. Our
proxy server is registered with the master server and is also working
ok for the most part.
