Users Guide

connection profile is always associated to a user role and all users belonging to that role will use the configured
settings. If you do not assign a VIA connection profile to a user role, the default connection profile is used.
Example
The following example shows a simple VIA connection profile:
(host) (config) #aaa authentication via connection-profile "via"
(host) (VIA Connection Profile "via") #server addr 202.100.10.100 internal-ip 10.11.12.13 desc
"VIA Primary" position 0
(host) (VIA Connection Profile "via") #auth-profile "default" position 0
(host) (VIA Connection Profile "via") #tunnel address 10.0.0.0 netmask 255.255.255.0
(host) (VIA Connection Profile "via") #split-tunneling
(host) (VIA Connection Profile "via") #windows-credentials
(host) (VIA Connection Profile "via") #client-netmask 255.0.0.0
(host) (VIA Connection Profile "via") #dns-suffix-list mycorp.com
(host) (VIA Connection Profile "via") #dns-suffix-list example.com
(host) (VIA Connection Profile "via") #support-email [e-mail]
Command History
Release Modification
ArubaOS 5.0 Command introduced
ArubaOS 6.1 The following commands were introduced:
l admin-logon-script
l admin-logoff-script
l ikev2-policy
l ikev2-proto
l ikev2-auth
l ipsecv2-crypto
l minimized
l suiteb-crypto
ArubaOS 6.1.3.2 The auth_domain_suffix parameter was introduced.
ArubaOS 6.2 The following commands were introduced:
l allow-whitelist-traffic
l banner-message-reappear-timeout
l controllers-load-balancing
l enable-fips
l enable-supplicant
l whitelist
ArubaOS 6.3 The user-idle-timeout parameter was introduced.
Dell Networking W-Series ArubaOS 6.4.x | User Guide aaa authentication via connection-profile | 84