VPN with SSTP not possible: 'Necessary secrets for the VPN connection were not provided.'

[der_vegi]

I am trying to setup a network connection with SSTP under a fresh install of Kubuntu. Yet independent of the option regarding the password storage, 'Ask for this password every time', 'Store password for all users/this user', I get the error 'Necessary secrets for the VPN connection were not provided.' and am never prompted for the password.

With my old install of Ubuntu 22.04 (upgrade from 20.04, then installed KDE), I could set up this connection in Gnome and then use it in KDE. But due to this bug in plasma-nm, I cannot set up this connection at all, as I do not have network-manager-gnome installed.

Is this maybe related to https://kde-bugs-dist.kde.narkive.com/XDXON3CW/plasma-nm-bug-360176-new-openconnect-fails-with-necessary-secrets-were-not-provided ? That would mean plasma-nm does not set up the required polkit rules.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: plasma-nm 4:5.24.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Jun 29 08:07:47 2022
InstallationDate: Installed on 2022-06-23 (5 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: plasma-nm
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Matthew Carpenter (matt-eisgr)]

I'm also using Kubuntu 22.04.2 and have the same problem.

I was looking for a good place to respond to
https://forums.gentoo.org/viewtopic-t-1040060-start-0.html
https://bbs.archlinux.org/viewtopic.php?id=150288

because it seems this is still an issue. Manually adding the polkit rule (listed in these two posts) resolved my issue.

I discovered this:
https://bugs.kde.org/show_bug.cgi?id=360176

which seems to indicate that is "RESOLVED INTENTIONAL" in 2016.
Why this is intended behavior I have no idea.

But I guess I know not to hold my breath. Thank God for Google Searches, since I couldn't find any other documentation to set this up correctly.

What gives?

[Scarlett Gately Moore (scarlettmoore)]

This bug https://bugs.kde.org/show_bug.cgi?id=356587 shows it was fixed. Please enable backports and updgrade and report back it fixes the issue. Thanks