Bug 338650

Summary: [RFE] [Openconnect] Add support for HOTP to OpenConnect VPN authenticator
Product: [Plasma] plasma-nm Reporter: David Woodhouse <dwmw2>
Component: generalAssignee: Lukáš Tinkl <lukas>
Status: REPORTED ---    
Severity: wishlist CC: dataforce, dwmw2, jgrulich, keplicz
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

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. ***