https://bugs.kde.org/show_bug.cgi?id=424678
Bug ID: 424678
Summary: Plasma-nm does not register to NetworkManager with
NM_SECRET_AGENT_CAPABILITY_VPN_HINTS
Product: plasma-nm
Version: 5.18.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jgrul...@redhat.com
Reporter: emele...@gmail.com
Target Milestone: ---
SUMMARY
The registration process for plasma-nm to the NetworkManager system does not
provide for interactive secret management, precluding runtime secret handling
for plasma and other agents
STEPS TO REPRODUCE
1. Setup a VPN that needs runtime secrets, such as a fortisslvpn with 2FA after
login
2. Try to bring the VPN up with nmcli
3.
OBSERVED RESULT
NetworkManager fails with the messages
Calling old Connect function as not all agents support interactive secrets
ERROR: Failed to get PIN:
GDBus.Error:org.freedesktop.NetworkManager.Settings.Connection.Failed: More
secrets required but cannot ask interactively
Actually, it is plasma-nm that prevents interactively asking, since if I stop
plasma-nm, then the message no longer appears and nmcli works as expected
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
