OpenVPN does not prompt password screen and missing 2FA support

[timmeijers]

Whenever I want to connect my OpenVPN I ran into a couple of issues. I was able to get workarounds for all of them gladly.

1. When you import the OpenVPN configuration file and you try to turn it on it won't work. Because my OpenVPN connection requires a password to be present. There is no prompt for this, however if you set it up in the settings manually it would be ok.
2. When you connect to OpenVPN there is an option to have 2FA, though not really documented well. When I try to connect with my VPN provider having turned this on, I again do not get this prompt, and also not possible to configure (would be inconvenient if I could, because its time-based, but no work-around).

To connect to my VPN I made a bash alias called vpn, calling nmcli con up {connectionname} --ask which is enough to make it ask for the prompts in the console first the password, then after that the OTP.
3. However the otp code overwrites my password value, meaning i have to the password again every time.

To at least have prompts work again, for both password and otp would be great. An extra nice to have (but not sure if this is something you guys can control) to have it not save/overwrite the otp value onto the password value.

[wash2]

There should be a password prompt, what version of cosmic-settings do you have installed?

[georg-brunner]

Hi,

I think I can confirm the part about 2FA.
The VPN of my university requires username, password and one-time password.
I can connect via command line with nmcli --ask c up <vpn_name> (as mentioned above).
When I try to connect via cosmic-settings I am prompted for a username and password - however there is no field to enter a one-time password.

Thank you very much for all your effort!

[fluffinity]

I can confirm the above with passwords. When trying to connect to a configured VPN you actually get the error message of nm-cli directly in the prompt window. Here is how it looks:

This error happens on current Fedora 43 with Cosmic Settings version 0.1.0 .

So if I got the current control flow correct the chain looks like this:

1. User click on connect in Settings
2. nm-cli gets invoked without --ask and exits as a result
3. Settings creates and shows the username-password prompt
4. User clicks on Connect
5. Settings tries to send the input to nm-cli, which obviously fails as it does not wait for any user input
6. Nothing further happens

[Charlyo]

Can confirm on cosmic-settings 1.0.0-beta6