From the --dump-http output, it seems that the XML transaction is selecting incorrect tunnel-group and group-alias.
I attempted to patch a --no-xmlpost option into network-manager-openconnect, but in the process I figured out a strange workaround...
I am currently instructing my Ubuntu 13.10 users to press the 'connect' button in network-manager-openconnect TWICE RAPIDLY. For some reason, after the SSL socket is closed unexpectedly during the first connection attempt, the second attempt doesn't use XML Post, and authentication succeeds.
From the --dump-http output, it seems that the XML transaction is selecting incorrect tunnel-group and group-alias.
I attempted to patch a --no-xmlpost option into network- manager- openconnect, but in the process I figured out a strange workaround...
I am currently instructing my Ubuntu 13.10 users to press the 'connect' button in network- manager- openconnect TWICE RAPIDLY. For some reason, after the SSL socket is closed unexpectedly during the first connection attempt, the second attempt doesn't use XML Post, and authentication succeeds.