Ensure correct permissions on client-configs/*

[jameskirsop]

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 5.5
• Distribution: CentOS
• Module version: Latest

How to reproduce (e.g Puppet code you use)

Assign permissions that mean that OpenVPN can't read client-configs.

What are you seeing

OpenVPN server not providing the correct IP addresses to clients because it silently ignores client configuration files that it can't read. A client configuration file which had been recently generated for a new host had permissions which meant that the user/group openvpn was running as couldn't read it.

What behaviour did you expect instead

The module to ensure that the correct permissions are set on the files so that OpenVPN server can read them. In my instance this is 644.

This could have alternatively been solved if the files under client-configs had the group set to the user that openvpn was running as.

Any additional information you'd like to impart

I'm not entirely sure how my sever ended up in this state. It could possibly have been because the user/group permissions changes (see #352) that I tried to make and switched back when things went bad with Facter.