
RADIUS Overview
303538-A Rev 00
2-3
RADIUS Authentication
You configure RADIUS authentication on a slot-by-slot basis. Therefore, a call
designated for a RADIUS-configured slot performs authentication. If the router is
already using a slot for dial-on-demand, dial backup, or bandwidth-on-demand
service, you cannot configure this slot for authentication. This restriction does not
apply if the slot is configured with a demand circuit group that uses only one
demand pool. In this case, you can configure authentication.
When a remote user calls the RADIUS client, the client passes the call request,
referred to as the access challenge, to the RADIUS server. The access challenge
contains the user’s name and password. The server verifies the user’s identity and,
for authorized callers, responds with an access accept message, which includes
the required access information. This information is sent to the client, which
passes it to the remote user. If the remote user is not authorized, the server
responds with an access reject message.
The client can pass multiple requests to the server simultaneously. If the client
cannot reach the server, and you configured an alternate server, the client passes
the request to the alternate server.
The authentication process occurs only once for each call. Once RADIUS
authentication is complete, the remote user can communicate with the destination
network.
Using PPP for Dial-up Connections
The Bay Networks RADIUS client uses Point-to-Point Protocol (PPP) for the
dial-up line between itself and the remote user. When you configure RADIUS,
Site Manager automatically configures PPP for the client.
To identify itself to the server, the remote user uses the PPP Challenge Handshake
Authentication Protocol (CHAP) or Password Authentication Protocol (PAP). The
client includes the remote user’s CHAP name and secret or PAP ID and password
in the access challenge to the server.
Comentarios a estos manuales