then you're pretty good to go using OpenVPN Connect, just pointing the URL in the app at your web server with this REST API. If you implement both REST APIs providing the same profile, doing some proper username/password auth. But it makes a difference for AS servers, as some AS user accounts may have possibility to download both - which gives a different user behaviour. The OpenVPN Connect client should usually not care much about this difference, as this information is encoded in the downloaded config profile (as part of the certificate, config profile containing -auth-user-pass or not).

And the GetUserlogin will require the AS user to provide username/password. Since my last comment I rolled Windows up to control point at which OpenVPN worked. I also tried to remove completely OpenVPN, as it is written in the manual, but it did not help. The difference between the GetAutologin and GetUserlogin interfaces are AS specific, where the former one will essentially be a cert-only based authentication when connecting to the AS server. On freshly installed Windows 10, Openvpn installed normally (no errors). Since you implement this yourself, you might not care about 2FA enabled user authentication, which makes the server side simpler.

cd /home/user/Downloads/ & openvpn3 config-import -config client.ovpn) Share. home/user/Downloads/client.ovpn) or have shell in the directory already (e.g. I don't have any open server side implementation, but the OpenVPN 3 Linux project has an official AS download profile feature available - written in Python. When pointing programs at files using the command-line, you either need to give it the full path to the file (e.g. It's basic HTTP authentication over HTTPS, returning back a profile in plain/text. The REST API used by Access Server for profiles, is pretty simple.

Openvpn connect windows import error