Authenticating A Local Radius Server - Motorola WS5100 Series Migration Giude

9-8 WS5100 Series Switch Migration Guide

9.3.1.2 Authenticating a Local Radius Server

1. Click on Authentication
local Radius server.
a. Refer to the
Specify the
• PEAP
for networks using legacy EAP authentication methods.
• TTLS
until after a secure transport tunnel has been established. This allows EAPTTLS to protect legacy
authentication methods used by some RADIUS servers.
• If PEAP
menu. The options are GTC and MSCHAP-V2.
- Generic Token Card (GTC) — This is a challenge handshake authentication protocol that uses
a hardware token card to provide the response string.
- Microsoft CHAP (MSCHAP-V2)— This is an encrypted authentication method based on
Microsoft's challenge/ response authentication protocol.
• If TTLS
down menu. The options are MD5, PAP and MSCHAP-V2.
- Message Digest 5 (MD5)— This is a secure hash function which converts a long data stream
into a fixed size digest.
- Password Authentication Protocol (PAP)— This is a protocol where the user sends an
identifier and password pair to the server. This information is sent un-encrypted.
- Microsoft CHAP (MSCHAP-V2)— This is an encrypted authentication method based on
Microsoft's challenge/ response authentication protocol.
• Use Auth Data Source
tab in the main Radius Server window, to configure the authentication for the
Authentication section to define the following Radius authentication information.
EAP and Auth Type for the RADIUS server.
uses a TLS layer on top of EAP as a carrier for other EAP modules. PEAP is an ideal choice
is similar to EAP-TLS, but the client authentication portion of the protocol is not performed
is selected as the EAP type, specify a Auth Type for PEAP to use from the drop-down
is selected as the EAP type, specify a Default Auth Type for TTLS to use from the drop
drop-down menu to select the data source for the local RADIUS server.