A openconnect tem suporte nativo para Pulse Secure?

Question

Desde que lançaram o Pulse Secure no lugar do Network Connect, eu tenho tentado me conectar à VPN da minha empresa usando o openconnect.

Eu sou aparentemente capaz de rodar o openconnect sem erros, fazer o auth de 2 fatores, etc. mas subseqüentemente não consigo acessar as apis que vivem atrás do firewall.

Alguém sabe se o openconnect tem suporte nativo para Pulse Secure agora, ou ainda é experimental?

Por acaso estou trabalhando no Ubuntu 16.04 se isso for relevante.

> sudo openconnect --juniper --user=example remote.example.com
WARNING: Juniper Network Connect support is experimental.
It will probably be superseded by Junos Pulse support.
GET https://remote.example.com/
Connected to 123.45.67.89:443
SSL negotiation with remote.example.com
Connected to HTTPS on remote.example.com
Got HTTP response: HTTP/1.1 302 Found
GET https://remote.example.com/example/welcome.cgi
SSL negotiation with remote.example.com
Connected to HTTPS on remote.example.com
frmLogin
realm [Example 1|Example 2]:Example 1
frmLogin
password:
POST https://remote.example.com/example/login.cgi
SSL negotiation with remote.example.com
Connected to HTTPS on remote.example.com
Got HTTP response: HTTP/1.1 302 Moved
GET https://remote.example.com/example/welcome.cgi?p=more-cred&id=state_1234567890
SSL negotiation with remote.example.com
Connected to HTTPS on remote.example.com
frmLogin
user#2:example
password#2:
POST https://remote.example.com/example/login.cgi
SSL negotiation with remote.example.com
Connected to HTTPS on remote.example.com
Got HTTP response: HTTP/1.1 302 Moved
GET https://remote.example.com/example/starter0.cgi?check=yes
SSL negotiation with remote.example.com
Connected to HTTPS on remote.example.com
SSL negotiation with remote.example.com
Connected to HTTPS on remote.example.com
SSL negotiation with remote.example.com
Connected to HTTPS on remote.example.com
Connected as 10.10.10.10, using SSL