This seems to be a long standing issue dating back MANY years, but there seems to be no resolution implemented,
ex: NetworkManager don’t ask for TOTP via OpenVPN.
Improve 2FA handling
kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections
I am able to run the openvpn command via terminal and connect, but through NetworkManager, it never prompts for anything and eventually times out. I have attempted adding the password for the key and the username/password but nothing happens. While tailing the journalctl I get the following when attempting to connect:
Oct 25 11:08:14 hostname nm-openvpn[26903]: OpenVPN 2.6.12 [git:makepkg/038a94bae57a446c+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Jul 18 2024
Oct 25 11:08:14 hostname nm-openvpn[26903]: library versions: OpenSSL 3.3.2 3 Sep 2024, LZO 2.10
Oct 25 11:08:14 hostname nm-openvpn[26903]: DCO version: N/A
Oct 25 11:08:14 hostname nm-openvpn[26903]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Oct 25 11:08:14 hostname nm-openvpn[26903]: TCP/UDP: Preserving recently used remote address: [AF_INET]VPNIP:PORT
Oct 25 11:08:14 hostname nm-openvpn[26903]: UDPv4 link local: (not bound)
Oct 25 11:08:14 hostname nm-openvpn[26903]: UDPv4 link remote: [AF_INET]VPNIP:PORT
Oct 25 11:08:14 hostname nm-openvpn[26903]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Oct 25 11:08:15 hostname nm-openvpn[26903]: [VPNHOSTNAME] Peer Connection Initiated with [AF_INET]VPNIP:PORT
I know I can get around it by running openvpn, but I would much rather use NetworkManager and nmcli to connect to my networks.