Using More Than One Authentication Type In A Vsc; Deployment With A Controller - HP MSM3xx Management And Configuration Manual

WPA / WPA2 and 802.1X authentication
Full support is provided for users with WPA / WPA2 client software, and 802.1X client
software that uses the following:
 EAP-TLS: Extensible Authentication Protocol Transport Layer Security.
 EAP-TTLS: Extensible Authentication Protocol Tunnelled Transport Layer Security.
 PEAP: Protected Extensible Authentication Protocol.
Note
For security reasons, use of 802.1X without enabling dynamic WEP encryption is not
recommended.
MAC-based authentication
Devices can be authenticated based on their MAC address. This is useful for authenticating
devices that do not have a web browser (cash registers, for example). As soon as the device
MAC address appears on the network, the AP attempts to authenticate it.

Using more than one authentication type in a VSC

For added flexibility, you can enable both the 802.1X and VSC-based MAC authentication at
the same time. MAC authentication always takes place first. If it fails, 802.1X is then
attempted.

Deployment with a controller

Autonomous APs can also be used with a controller to create a public access network
infrastructure. In this type of deployment, all VSCs are access-controlled, which means that
the AP forwards all wireless user traffic to the controller which handles user authentication
and access control.
To reach protected network resources, wireless users must successfully authenticate with
the public access interface that is provided by the controller.
Public network
The following authentication types are supported on the controller: WPA / WPA2, 802.1X,
MAC, HTML. For more information on controller authentication features, see the MSM7xx
Controllers Management and Configuration Guide.
interface
LAN port
MAP
Controller
Public
access
Internet port
Working with VSCs
Key concepts
Protected network
Internet
4-3