After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 766239 - Needed mask OS option for define OS type (linux,linux-64,win,...)
Needed mask OS option for define OS type (linux,linux-64,win,...)
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: VPN: openconnect
1.2.x
Other Linux
: Normal normal
: ---
Assigned To: David Woodhouse
NetworkManager maintainer(s)
: 783846 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2016-05-10 19:39 UTC by Mikhail
Modified: 2017-06-28 08:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mikhail 2016-05-10 19:39:06 UTC 
When I try connect via NetworkManager GUI I got strange error <error id="9" param1="Your environment does not meet the access criteria defined by your administrator." param2="">Login denied.  %s</error>

So I got into CLI for investigate this issue. And able to connect connect with defined "--os" option.
My example:
openconnect --os=win 85.248.4.70

But I am still prefer GUI, I beg add this option in GUI.

Expected new combobox with values "Default", "Win", "Linux", "Linux 64".

Thanks.
Comment 1 Mikhail 2016-05-10 19:49:57 UTC 
Or another approach:
Not adding addition option, but automatic applying this hack if see message "Your environment does not meet the access criteria defined by your administrator."
Comment 2 Thomas Haller 2017-06-16 07:51:58 UTC 
*** Bug 783846 has been marked as a duplicate of this bug. ***
Comment 3 Dmitry 2017-06-27 22:49:21 UTC 
FYI - Implemented (patch available) in https://bugzilla.gnome.org/show_bug.cgi?id=782016
But not merged yet afaik.
Comment 4 Thomas Haller 2017-06-28 08:16:54 UTC 
Out of bug 782016, a patch was merged to master.

https://git.gnome.org/browse/network-manager-openconnect/commit/?id=9fbe2817da437f473cf46205e19c38d273adc600

This issue should be fixed now.

Closing. Please reopen if necessary.