Client configuration update

[romainb]

I have an openvpn server that serves access to a lot of roadwarriors. They all use unprivileged windows accounts, and the same config file.

In this situation, it's hard to manage and update this config file when we need to.
So, it would be nice to have the openvpn service to check for an update and replace (if needed) the config file.

This could be done by a --update-url [url to the config file]

OpenVPN clients would check the file before each start.

For security reasons, the URL should be https and the trusted CA of the website could be specified.

[Eric Crist]

This ticket is similar to the 'Configs from Server' wish list item on the forum. You can view this thread at ​http://forums.openvpn.net/viewtopic.php?f=10&t=2441

[David Sommerseth]

Maybe a silly question ... but why not have a --route-up script which does exactly this? Where this script download the proper configuration when the VPN is established?

[Samuli Seppänen]

There are plenty of hooks in openvpn for running scripts and executables at various phases of connection establishment, I think this ticket should be closed unless someone can show that the existing hooks are inadequate.

[Samuli Seppänen]

Adding to the previous comments... there is always the option of using some external configuration management system to update the client configuration files. This way you're not solving the configuration update issue for just OpenVPN, but for whatever other applications you might have on the client computers.

Closing the ticket.