Hi Michael,
I'm facing a similar problem, *probably *after adding our internal AD CA to:
/etc/pki/ca-trust/source/
anchors/
and run:
update-ca-trust
(to use LDAPS as authentication source for Web GUI).
Now, from the Capsule server, command:
/etc/puppet/node.rb myclient.mydomain.com
doesn't work
Hi Michael,
I'm facing a similar problem, *probably *after adding our internal AD CA to:
/etc/pki/ca-trust/source/anchors/
and run:
update-ca-trust
(to use LDAPS as authentication source for Web GUI).
Now, from the Capsule server, command:
/etc/puppet/node.rb myclient.mydomain.com
doesn't work
Our solution for this problem is simply to create a new ca.pem file, which
is just a concat of our (internal AD ca) + (puppet ca). We deploy this new
"foreman-web-ca" on both the foreman servers and puppetmasters, then
reference it in foreman's httpd.conf and the puppetmaster's
/etc/puppetlabs/
I know this is an older and revived thread, but was anyone able to get this
working?
We are using puppetca signed certs, but would like our web browser to be
from our internal AD ca so all our windows machines trust it.
We have followed articles at
https://theforeman.org/2015/11/foreman-ssl.html
