Users Guide

Table Of Contents
Dell PowerConnect ArubaOS 5.0 | User Guide 802.1x Authentication | 253
Figure 44 802.1x Authentication with RADIUS Server
The supplicant and authentication server must be configured to use the same EAP type. The controller does not
need to know the EAP type used between the supplicant and authentication server.
For the controller to communicate with the authentication server, you must configure the IP address,
authentication port, and accounting port of the server on the controller. The authentication server must be
configured with the IP address of the RADIUS client, which is the controller in this case. Both the controller and
the authentication server must be configured to use the same shared secret.
The client communicates with the controller through a GRE tunnel in order to form an association with an AP
and to authenticate to the network. Therefore, the network authentication and encryption configured for an
ESSID must be the same on both the client and the controller.
Authentication Terminated on Controller
User authentication is performed either via the controller’s internal database or a non-802.1x server. See “802.1x
Authentication Profile Basic WebUI Parameters” on page255 for an overview of the parameters that you need to
configure on 802.1x authentication components when 802.1x authentication is terminated on the controller
(AAA FastConnect).
Client
(Supplicant)
WLAN Switch
(Authenticator)
Authentication
Server
• Server IP
• Shared Secret
• Auth Port
• Acct Port
• Client IP
• Shared Secret
• ESSID
• Network Authentication
• Data Encryption
• ESSID
• Network Authentication
• Data Encryption
• EAP Type• EAP Type
Note: Additional information on EAP types supported in a Windows environment, Microsoft supplicants, and authentication
server, is available at http://technet.microsoft.com/en-us/library/cc782851(WS.10).aspx.