Bug 455438 - Fortinet VPN doesn't wait for DUO/2FA answer long enough
Summary: Fortinet VPN doesn't wait for DUO/2FA answer long enough
Status: RESOLVED DUPLICATE of bug 445466
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_networkmanagement (other bugs)
Version First Reported In: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-16 19:33 UTC by Vladimir
Modified: 2024-12-23 18:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir 2022-06-16 19:33:43 UTC
SUMMARY
When using Fortinet paired with DUO 2FA the Network Manager Openforticlient applet waits only 2-3 seconds before giving up, this means you miss the opportunity to approve the connection 99% of the time.

This doesn't happen with the openfortivpn client used as a CLI app.

STEPS TO REPRODUCE
1. Have your Fortinet VPN setup with DUO 2FA
2. Try to connect to your VPN
3. Wait 5 seconds, the connection attempt is dropped

OBSERVED RESULT
the connection attempt is dropped before you can approve in DUO

EXPECTED RESULT
the connection attempt is should wait the same time as the CLI version (30 seconds?) for the approval before giving up

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 21.10
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Robert 2023-05-04 06:43:22 UTC
My company recently enabled 2fa for openfortivpn, and I'm having a similar issue.
Only the dialog closes immediately after opening, instead of giving me 3 seconds.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
Archlinux kernel: 6.2.13-arch1-1
OpenFortiVPN: 1.20.1
Comment 2 Robert 2023-07-04 11:52:33 UTC

*** This bug has been marked as a duplicate of bug 445466 ***