User authentication, accounts, and addressing
No authentication
10-26
No authentication
For applications where a remote device performs all authentication functions, it can be
useful to disable authentication on the controller and instead, forward all traffic on a VSC
into an egress GRE tunnel or egress VLAN for authentication by the remote device.
Note Because the controller routes traffic to the VSC egress, L2 information from the user is lost
and only L3 information is available to the remote authentication device.
Locally-defined user accounts
The controller provides support for locally-defined user accounts with a wide range of
customizable options. Locally-defined user accounts use the integrated RADIUS server.
Configuration of these accounts is done using the options on the Controller >> Users menu,
which includes the following configuration pages: User accounts, Account profiles,
Subscription plans, and Session persistence.
Each user account:
Obtains account properties from one or more account profiles.
Obtains account durations from one or more subscription plans.
Is restricted for use with one or more VSCs.
Features
Access control
Two types of local user accounts are available: access-controlled and not access-controlled.
Access-controlled accounts must be used with a VSC that is configured to provide access
control.
Non-access-controlled accounts must be used with a VSC that is not configured to
provide access control. These accounts are used to handle authentication directly at the
AP and cannot make use of the access control capabilities of the controller (the
controller must not be in the traffic data path).
Validity and subscription plans
Each user account can be associated with a subscription plan that defines:
The time period during which the account is available.
The total amount of time a user can be online when logged in with the account.
To Next Page
Loading...
Need help?
General
