On Tue, Jul 16, 2013 at 2:05 PM, Dmitry Eremin-Solenikov <dbaryshkov at gmail.com> wrote: > After a recent update our VPN server, I noticed that openconnect is not > able anymore to connect to it. To login to our VPN server I have to > select non-default auth group. According to http traffic dumps OpenConnect > 5.01 tried to select a group, but server failed to respond properly. > After analysing dumps from official client, I noticed that it passes a > group in the "init" XML request. I created a simple workaround, that > passes group to the "init" request, if it was selected via command line > prompt. Full solution should include reselecting a group, however it > looks like it requires auth traffic restart, which is too intrusive > change. This sounds related to a known issue: http://lists.infradead.org/pipermail/openconnect-devel/2013-June/001081.html David had some thoughts on how to change the control flow to fix it: http://lists.infradead.org/pipermail/openconnect-devel/2013-June/001088.html
