Filter
Top Products
308 CHAPTER 8: CONFIGURING AUTHENTICATION, AUTHORIZATION, AND ACCOUNTING PARAMETERS
The EAP-MD5 option does not work with Microsoft wired authentication
clients.
PEAP—Protected EAP with Microsoft Challenge Handshake
Authentication Protocol Version 2 (MS-CHAP-V2). Select this protocol
for wireless clients.
Uses TLS for encryption and data integrity checking.
Provides MS-CHAP-V2 mutual authentication.
Only the server side of the connection needs a certificate.
Local EAP-TLS—EAP with TLS.
Provides mutual authentication, integrity-protected negotiation,
and key exchange.
Requires X.509 public key certificates on both sides of the
connection.
Provides encryption and integrity checking for the connection.
Cannot be used with RADIUS server authentication (requires user
information to be in the switch’s local database)
Pass-Through—No protocol is used by the WX. 3Com Mobility
System Software (MSS) sends the EAP processing to a RADIUS server.
If you select PEAP, the EAP Sub-Protocol is MS-CHAPV2. For other
protocols, there is no the EAP Sub-Protocol to select.
6 Click Next.
7 If the authentication rule is disabled, select Enabled.
When a rule is disabled, 3WXM does not add it to the switch’s
configuration.
8 Select the authentication method(s) in the Available RADIUS Server
Groups list and click Add.
An authentication method specifies where the switch will look for user
information to authenticate users. You can select a RADIUS server group,
LOCAL (the switch’s local user database), or both.
MSS tries the methods in the order they appear in the Current RADIUS
Server Groups list. To reorder the methods, select a method and click Up
or Down.