https://bugs.kde.org/show_bug.cgi?id=414975

--- Comment #3 from Gaël de Chalendar (aka Kleag) <kle...@gmail.com> ---
Well, in fact, I was wrong about the port. 443 is the default HTTPS port and
seems to be the default in new versions of [1] (current github version is
1.11.0). In the version used on KDE Neon (1.6.0), setting the port in the
configuration file was mandatory.

BTW, an empty password field was also mandatory in the configuration file even
when using one-time passwords. It is not anymore, it seems. But this is
probably not interesting for my current pb with the plasma openfortivpn nm
applet.

I tried with the latest openfortivpn version and got different errors:

NetworkManager[1060]: <info>  [1576139547.1460]
settings-connection[0x561b296e4b60,2a77d541-0d9e-417e-9f47-d3efda16f6ff]:
write: successfully updated (keyfile: update
/etc/NetworkManager/system-connections/XXX
(2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX")), connection was modified in the
process
NetworkManager[1060]: <error> [1576139547.1495]
vpn-connection[0x561b29724390,2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX",0]:
final secrets request failed to provide sufficient secrets

The /etc/NetworkManager/system-connections/XXX content is:
[connection]
id=XXX
uuid=2a77d541-0d9e-417e-9f47-d3efda16f6ff
type=vpn
permissions=user:xxx:;

[vpn]
gateway=<host>
otp-flags=2
password-flags=2
trusted-cert=xxx
user=XYZ
service-type=org.freedesktop.NetworkManager.fortisslvpn

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto



[1] https://github.com/adrienverge/openfortivpn

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to