I think I've figured out the point of failure. It seems the problem is with mod_jk and the encryption it uses for for it's proxy. Right now mod_jk uses mod_ssl for it's proxy to tomcat, but it isn't using mod_nss. Now I'm not sure if this is because it just can't support that, or if there is something I'm doing inherently wrong.
> Hi > > I'm trying to setup Spacewalk on a Server that already has FreeIPA. > FreeIPA uses mod_nss, and mod_nss can't coexist with mod_ssl. > > I assumed that mod_ssl and the associated cert that is used is only for > the HTTPS proxy that is used. So what I did was add the cert and key in > /etc/pki/tls/certs/spacewalk.cert and /etc/pki/tls/private/spacewalk.key > into the nss db that FreeIPA already uses. > > Unfortunately this only gets me the usual 404 error i get with no cert. I > also took out the SSLProxyEngine in > /etc/httpd/conf.d/zz-spacewalk-www.conf, in order to allow Apache to load. > > I'm assuming my assumptions were correct and this would be the correct > course of action to take, so I'm where else the mod_ssl directly affects > the web front end. I want to try and move this to mod_nss so that these > two projects can coexist on a single machine. > > This didn't seem appropriate for the normal users list so I'm sorry if > this should actually belong on that list. > > Thanks, > Shyam > > > _______________________________________________ > Spacewalk-devel mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-devel > _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
