From: Daniel Lenski Date: Wed, 28 Aug 2019 23:43:27 +0000 (-0700) Subject: explain GlobalProtect portals vs. gateways in the docs X-Git-Tag: v8.06~103^2 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=2a1b1327134934ccd3be92fc087b7462f5c24e0e;p=users%2Fdwmw2%2Fopenconnect.git explain GlobalProtect portals vs. gateways in the docs Signed-off-by: Daniel Lenski --- diff --git a/www/globalprotect.xml b/www/globalprotect.xml index 3984b3c8..f863a781 100644 --- a/www/globalprotect.xml +++ b/www/globalprotect.xml @@ -22,6 +22,38 @@ to the command line: openconnect --protocol=gp vpn.example.com

+

GlobalProtect portals and gateways

+ +

GlobalProtect VPNs actually contain two different server +interfaces: portals and gateways. Most VPNs have one portal server and +one or more gateway servers; the server hosting the portal interface +often hosts a gateway interface as well, but not always. The portal +interface mostly sends centrally-imposed security/lockdown settings +for the official client software to follow. The only information sent +by the portal that's clearly useful to a VPN client like OpenConnect +(which tries to give full control to the end user) is the list of +gateways.

+ +

Some GlobalProtect VPNs are configured in such a way that the +client must authenticate to the portal before it can access the +gateway, while with other VPNs no interaction with the portal is +necessary. In order to replicate the behavior of the official +clients, OpenConnect first attempts to connect to the portal interface +of the specified server.

+ + +

Authentication

To authenticate, you connect to the secure web server (POST