Bug 338650

Summary:	[RFE] [Openconnect] Add support for HOTP to OpenConnect VPN authenticator
Product:	[Plasma] plasmashell	Reporter:	David Woodhouse <dwmw2>
Component:	Networking in general	Assignee:	Lukáš Tinkl <lukas>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	CC:	dataforce, dwmw2, jgrulich, keplicz, nate
Priority:	NOR
Version First Reported In:	master
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description David Woodhouse 2014-08-29 11:24:35 UTC

OpenConnect 6.00 adds proper support for HOTP tokens. We've had HOTP support for a while but it's been kind of unusable until now. HOTP is counter-based and you need to increment the counter each time you use a tokencode. But we had no way to *store* the updated counter. Now we do... you call the new openconnect_set_token_callbacks() function and give it a callback function it can call when it's updated the token. And we store it in the NM secrets — which means we have to migrate it from the configuration 'data' section to the 'secrets' section.

See https://git.gnome.org/browse/network-manager-openconnect/commit/?id=b3815e96
and https://git.gnome.org/browse/network-manager-openconnect/commit/?id=5e899ec0

Comment 1 Jan Grulich 2014-08-29 11:27:22 UTC

Just adding some documentation:

http://www.infradead.org/openconnect/token.html

Comment 2 Jan Grulich 2016-07-19 13:42:58 UTC

*** Bug 365807 has been marked as a duplicate of this bug. ***

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

Bulk transfer as requested in T17796

Comment 4 Nate Graham 2025-06-04 19:33:50 UTC

Thanks for the suggestion, and I'm sorry we were not able to look into this yet! Can you still reproduce the issue in Plasma 6.3.5 or later, and also presumably with a newer version of NetworkManager? It's possible it's been implemented or fixed by now. Thanks a lot!

Comment 5 Bug Janitor Service 2025-06-19 03:47:48 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2025-07-04 03:47:44 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.