Bug 405382

Summary:	[Openconnect] Cannot connect to VPN - asks for PKS#12 pass phrase
Product:	[Plasma] plasmashell	Reporter:	Ovidiu-Florin BOGDAN <kde.kfoar>
Component:	Networking in general	Assignee:	Jan Grulich <jgrulich>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	jgrulich, nate
Priority:	NOR
Version First Reported In:	master
Target Milestone:	1.0
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	VPN connection in Plasma UI VPN connection in GNOME UI

Description Ovidiu-Florin BOGDAN 2019-03-12 07:03:21 UTC

SUMMARY
I wouldn't have realised this was a bug in plasma-nm until I tested the same connection in NM in both Plasma and GNOME.

A Cisco AnyConnect VPN connection using a PKS#12 (.p12) key is asking for the key pass phrase in the Plasma UI and cannot connect due to that, but does not in the GNOME UI, and the connection works without issues. I'm asuming because of this that the connection certificte does not or has an empty pass phrase set when created.

I need advice on how to provide more details on this network connection, so this bug can be fixed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 28 KDE
(available in About System)
KDE Plasma Version: 5.13.4
KDE Frameworks Version: 5.48.0
Qt Version: 5.11.1

Comment 1 Ovidiu-Florin BOGDAN 2019-03-12 07:22:43 UTC

Created attachment 118736 [details]
VPN connection in Plasma UI

Comment 2 Ovidiu-Florin BOGDAN 2019-03-12 07:23:02 UTC

Created attachment 118737 [details]
VPN connection in GNOME UI

Comment 3 Ovidiu-Florin BOGDAN 2019-03-12 07:23:40 UTC

I've attached screenshots of the same VPN connection from both UIs for comparison.

Comment 4 Ben Cooksley 2024-12-23 18:23:42 UTC

Bulk transfer as requested in T17796

Comment 5 Nate Graham 2025-06-20 17:07:05 UTC

Hello, and sorry we weren't able to get to this yet. Can I ask you to check and see if the issue is still happening in Plasma 6.3.5? Thanks a lot!

Comment 6 Ovidiu-Florin BOGDAN 2025-06-23 06:40:39 UTC

Hello,

I can no longer test this, since I no longer have access to that VPN.

Since I can't reproduce this anymore, and from the looks of it, it's either fixed or not reproducible, I'll close this issue.