Description of problem:
After importing a valid OVPN config file, the "User private key" remains unset, and the connection cannot be saved.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open VPN settings panel.
2. Import some valid OVPN file.
The "User private key" variable remains unset showing the value "none".
The "User private key" variable is set to the correct value.
- When importing indivudal PEM files, then the VPN connection can be saved and activated successfully. However, when opening the corresponding configuration panel again, then "User private key" shows the value "none". The connection cannot be saved or updated unless the corresponding PEM file has been selected again.
- This bug is a regression with respect to Fedora 31 for which valid OVPN configuration files can be imported flawlessly.
Same issue here.
(In reply to Alessio from comment #1)
> Same issue here.
In addition. If you add the key by hand, you are able to save the connection and it also work.
But if you open the configuration in order to make some changes, you have to define the User private key again in order to be able to save the configuration.
Probably this is tracked upstream https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/50
It seems that it has been fixed upstream https://gitlab.gnome.org/GNOME/libnma/-/commit/b09c4dc2a8d3d7d44b9fc7ec22d499b7641de8c5