After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 777378 - Unable to remove VPN secrets over DBus
Unable to remove VPN secrets over DBus
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: VPN (general)
1.4.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-01-17 10:46 UTC by Jan Grulich
Modified: 2020-11-12 14:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jan Grulich 2017-01-17 10:46:03 UTC
Hi,

it seems to be not possible remove VPN secrets which have been previously wrongly set. When passing empty map or not passing secrets back at all using DBus update() method in o.f.NetworkManager.Settings.Connection interface doesn't have any effect and previous secrets still exist. Also trying to use empty values for secrets which are already set produces error about empty value.

Would be nice for NM to accept either empty map or when someone passes full map with only "data" property without "secrets" property to override current secrets.
Comment 1 Jiri Klimes 2017-01-19 12:09:33 UTC
The Update() call has been changed some time ago. It doesn't clear secrets when the passed data doesn't contain any secrets, because it caused problems and the Update() was cumbersome. See bug 728920.

Instead, ClearSecrets() call has been introduced for removing secrets.
https://developer.gnome.org/NetworkManager/stable/gdbus-org.freedesktop.NetworkManager.Settings.Connection.html
Comment 2 André Klapper 2020-11-12 14:27:49 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).