SSL setup¶

The smart proxy can work in SSL mode, where both sides verify and trust each other.

Configure SSL certificates¶

This request will only be accepted if the SSL certificates match. Therefore the client's private key grants access to proxy's funtionality, so protect it.

As this tool is meant to interoperate with a puppet installation I suggest that you use the Certificate Authority provided by a puppet server as your CA.

1. Login to your puppetmaster, which has a Certificate Authority
2. Use the puppet tools to create a new certificate
   

   
     puppetca --generate <proxy-FQDN>
   

3. Copy the certificate keys to your Windows host
   

   
       scp puppetmaster:/var/lib/puppet/ssl/ca/signed/<proxy-FQDN>.pem signed.pem
       scp puppetmaster:/var/lib/puppet/ssl/private_keys/<proxy-FQDN>.pem private.pem
   

4. Copy the ssl/certs/ca.pem from any puppet client to the smart-proxy\config directory. This ensures that the proxy trusts the same CA as a puppet client.

Troubleshooting¶

Unable to save
Unable to communicate with the proxy: No such file or directory - /.puppet/var/ssl/certs/foremanserver.domainname.corp.pem
Please check the proxy is configured and running on the host before saving.

Workaround

1. mkdir /.puppet
2. ln -s /var/lib/puppet/ /.puppet/var
3. add foreman, foreman-proxy to puppet group
4. chmod -R 640 /var/lib/puppet/ssl/private_keys
5. chgrp -R puppet /var/lib/puppet/ssl/private_keys #

Example 2:
I also ran into this issue ... here is my breakdown of it.

This seems to stem from the foreman webserver needing access to it's certificate. It looks for it down the webuser home directory for .puppet which somewhat is supposed to mimic the puppetdir.

So for my SLES system which:

• Webuser - wwwrun
• Webuser homedir - /var/lib/wwwrun
• Puppet dir - /etc/puppet

Looks in /var/lib/wwwrun/.puppet/ssl/certs

So I needed to:

add wwwrun to puppet group
cd /var/lib/wwwrun
ln -s /etc/puppet .puppet
chgrp -R puppet /etc/puppet/ssl/private_keys
chmod 640 /etc/puppet/ssl/private_keys/*