client-config (Juniper Secure Connect)
Syntax
client-config name { biometric-authentication; domain-name domain-name; certificate { no-expiry-warning; no-pin-request-per-connection; warn-before-expiry days; } connection-mode (always | manual); dead-peer-detection { interval seconds; threshold threshold; } no-dead-peer-detection; no-eap-tls; no-tcp-encap; windows-logon { auto-dialog-open; disconnect-at-logoff; domain domain; eap-auth; flush-credential-at-logoff; lead-time-duration seconds; mode (automatic | manual); } }
Hierarchy Level
[edit security remote-access]
Description
Define Juniper Secure Connect remote client configuration parameters. The parameters define how Juniper Secure Connect client establishes VPN tunnel with your security device.
Options
name |
Name of configuration object name. |
||||
biometric-authentication |
Enable biometric authentication. |
||||
domain-name | Define the set of search domain name. As a system administrator, you can
configure the set of search domain name that the Juniper Secure Connect
application will use to handle DNS lookups. This is applicable to both full
tunnels and split tunnel configurations. You can provide more than one
search domain names by executing the Range: 0-1023 characters including comma. |
||||
connection-mode |
Set one of the following connection mode for clients:
|
||||
dead-peer-detection— |
Enable dead-peer-detection on the client.
|
||||
no-dead-peer-detection |
Disable dead-peer-detection on client |
||||
no-eap-tls |
Disable EAP-TLS IKEV2 method. |
||||
no-tcp-encap |
Disable tcp encapsulation. |
||||
windows-logon |
Specify windows logon options. |
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
security
Release Information
Statement introduced in Junos OS Release 20.3R1.
Support for domain-name
option at the [edit security
remote-access client-config name]
hierarchy level
added in Junos OS Release 22.1R1.