make F5 and Fortinet tests go through config-pulling (up to the point of tunnel connection), rather than stopping after authentication
The fake servers don't actually implement the tunnel, but they do implement
the pre-tunnel configuration endpoints, and then simulate a "cookie rejected"
response upon tunnel connection.
OpenConnect distinguishes cookie rejected via an exit status of 2, whereas
any other failure results in an exit status of 1.
Signed-off-by: Daniel Lenski <email address hidden>
This tests OpenConnect's ability to authenticate with a (fake) F5
server, using username+password (the only option that OpenConnect
currently supports).
The fake F5 authentication server requires python3 and Flask.
Signed-off-by: Daniel Lenski <email address hidden>
This tests OpenConnect's ability to authenticate with a (fake) Fortinet
server, using all of the options that OpenConnect currently supports
(username+password, username+password+token, non-default realm).
The fake Fortinet authentication server requires python3 and Flask.
Signed-off-by: Daniel Lenski <email address hidden>