Credentials with OTP for OpenVPN Connect

Hello Tom,

Thank you for reaching out, happy to help.

The behavior you're seeing is expected. With the OpenVPN Connect entry, RDM launches the client and loads the correct profile, but the OpenVPN Connect client does not support receiving the username, password, or OTP from an external application. This is a limitation of OpenVPN Connect itself (its command-line interface doesn't allow credentials to be passed in), so RDM cannot auto-fill them for that entry type.
If automatic authentication including a configured OTP is your goal, the supported approach is the OpenVPN GUI entry, which uses the OpenVPN 2.x GUI client (11.15.0.0 or later). You can find the full setup, including handling passwords with special characters, here: https://docs.devolutions.net/rdm/kb/troubleshooting-articles/openvpn-workaround/

Best regards,

Hello Eduard,

I know it's a very late reply ...

I have installed now OpenVPN GUI instead of OpenVPN Connect but I have an issue with the username and password field.

When I try to establish a connection and OpenVPN GUI comes up username field is already filled with the username used the connection before. So the RDM starts typing username in the password field and that's why it fails.
I also tried to configure the entry without a username but this didn't work either.

How can I solve this problem?

Kind regards, Tom

Ok, I found a solution for me.

I have configured an event before connection to the VPN.
I run a command line to delete the username entry from the registry. OpenVPN stores the username in HKCU\Software\OpenVPN-GUI\configs\...

"conhost.exe --headless reg.exe delete "HKCU\Software\OpenVPN-GUI\configs\MYPROFILENAME" /v "username-enc" /f"

After this the username files is empty and RDM can fill this filed correctly with the username and after this the password + OTP.