mirror of
https://github.com/os-mnemo/pan-globalprotect-okta
synced 2026-07-31 15:54:36 +02:00
Tino Lange
29527325fd
This fixes Issue https://github.com/arthepsy/pan-globalprotect-okta/issues/17 raised by @lvml. (Note that if you need to specify a client certificate for the `vpn_url`, then most probably you will also need to give the same certificate to the final `openconnect` call with `--certificate` via the `openconnect_args`)
18 lines
803 B
Plaintext
18 lines
803 B
Plaintext
debug = 0
|
|
vpn_url = https://vpn.example.com
|
|
okta_url = https://example.okta.com
|
|
username = myuser
|
|
password = mypass
|
|
# mfa_order = totp sms
|
|
sms.okta = 0
|
|
totp.okta = ABCDEFGHIJKLMNOP
|
|
totp.google = ABCDEFGHIJKLMNOP
|
|
gateway = Manual ny1-gw.example.com
|
|
#cert = path-to-client-cert-as-unencrypted-pem-file.pem
|
|
#openconnect_cmd = sudo openconnect
|
|
openconnect_args = # optional arguments to openconnect, probably you might want to repeat the cert here (if used above) with --certificate=xxx
|
|
execute = 0 # execute openconnect command
|
|
another_dance = 0 # second round of authentication required
|
|
bug.nl = 0 # newline work-around for openconnect
|
|
bug.username = 0 # username work-around for openconnect
|