It's works, but after couple of weeks I have some problems:
1. When I opened foreman URL, web browser asked me for user certifcate for
authentification. When I clicked cancel, a could normaly log in.
It isn't a big problem, but i'm corious why it's happening.
2. When i restarted service p
After I did a foreman-install, with site modified entries in the above
options, I still had foreman_proxy failing.
What seems to have fixed it was to:
1. Setup the lines in the foreman-answers.yaml under the forman_proxy
section to be:
ssl_ca: /etc/puppetlabs/puppet/ssl/certs/ca.pem
ssl_c
I think the simple thing is that the developers haven't directly supported
and tested using custom certs for the WebUI.
I'm just a user who ran into the same problem as the original poster...
My answer above was what I found I needed when I built a VM with the
foreman.org 1.12 installation instr
Did something change in Foreman 1.12.3 then? I did exactly as you showed,
but it broke Puppet.
On the verbose output from Foreman I get the error:
[ERROR 2016-09-30 19:20:14 verbose]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[*myhostfqdn*]:
Could not evaluate: Exception SSL_co
It works.
Thank you very much!
W dniu wtorek, 20 września 2016 18:54:48 UTC+2 użytkownik Edward Berger
napisał:
>
>
> I know there's some SElinux magic, but if you have disabled SELinux you
> can try a command line like
> this to install a new web certificate, key, and chain (intermediate
> ce
I know there's some SElinux magic, but if you have disabled SELinux you can
try a command line like
this to install a new web certificate, key, and chain (intermediate
certificates) and keep the puppet part working...
foreman-installer \
--foreman-server-ssl-key=/etc/pki/tls/private/foreman.exa
