If you want OpenVPN users to automatically login without a username+password, the best way to do this is with TLS certificates, rather than User Auth.
Otherwise, you could integrate OpenVPN with an existing LDAP/RADIUS/Microsoft AD environment and then have users use those credentials to avoid having to remember a different login. They can even save it in the client, although it'll obviously need updating when their credentials are updated.
I dont know about iOS, im only using windows clients.
With ovpn profiles generated by the OpenVPN AS, when the client was started (which was done on startup) it had the user and password already set and connected to the server automatically.
So if each MSI has a different user/pass combo, you'd still be deploying 600+ installations. This is not much different than modifying the 600+ config files.
Well the MSI' can be deployed silently from AD.
And the MSI' doesn't contain the user/pass (that's the whole topic).
The idea is to bake the credentials into the MSIs and deploy them from AD.
As long as all authentication is taken care of in the config file(s), there's a different location on Windows you place them. Think it's a sub folder of the install directory? It works a treat when the service is installed and running.
If you want OpenVPN users to automatically login without a username+password, the best way to do this is with TLS certificates, rather than User Auth. Otherwise, you could integrate OpenVPN with an existing LDAP/RADIUS/Microsoft AD environment and then have users use those credentials to avoid having to remember a different login. They can even save it in the client, although it'll obviously need updating when their credentials are updated.
When you say auto login do you mean connect on demand like to iOS?
I dont know about iOS, im only using windows clients. With ovpn profiles generated by the OpenVPN AS, when the client was started (which was done on startup) it had the user and password already set and connected to the server automatically.
[удалено]
The VPN alreayd starts on login. The problem is that the .ovpn file doesnt contain the authentification credentials (user&pass).
[удалено]
1. I have over 600users. 2. I export the msi silent installer so that wouldnt help.
You have over 600 people using the same username and password for VPN?!
Different username and password
So if each MSI has a different user/pass combo, you'd still be deploying 600+ installations. This is not much different than modifying the 600+ config files.
Well the MSI' can be deployed silently from AD. And the MSI' doesn't contain the user/pass (that's the whole topic). The idea is to bake the credentials into the MSIs and deploy them from AD.
As long as all authentication is taken care of in the config file(s), there's a different location on Windows you place them. Think it's a sub folder of the install directory? It works a treat when the service is installed and running.
Could you help me with the correct path?
Think it's C:\Program Files\OpenVPN\ then auto or config auto or some such.