mirror of
https://github.com/os-mnemo/pan-globalprotect-okta
synced 2026-07-31 07:44:38 +02:00
Implement config option cert to use a client certificate.
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`)
This commit is contained in:
+2
-1
@@ -8,8 +8,9 @@ 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
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user