Authentication and authorization between multiple RADIUS servers
A RADIUS authentication and authorization role is a function within a RADIUS-based wireless controller configuration that:
-
allows authentication and authorization duties to be carried out by a single RADIUS server or split between different servers
-
enables the controller to relay authentication attributes to a separate authorization server, and
-
in a split configuration, requires both servers to return ACCESS-ACCEPT for a client session to be established.
Cisco Embedded Wireless Controller on Catalyst Access Points use a request and response transaction with a single RADIUS server that combines both authentication and authorization.
A RADIUS server can assume the role of either an authentication server, authorization server, or both. In cases where there are separate RADIUS servers for authentication and authorization, the Session Aware Networking (SANet) component on the embedded wireless controller allows authentication on one server and authorization on another when a client joins embedded wireless controller.
Authentication can be performed using Cisco ISE, Cisco Catalyst Center, Free RADIUS, or any third-party RADIUS Server. After the authentication server successfully authenticates a user, the embedded wireless controller relays attributes received from the authentication server to another RADIUS server designated as the authorization server.
The authorization server then performs these:
-
Processes received attributes with the other policies or rules defined on the server.
-
Derives attributes as part of the authorization response and returns them to the embedded wireless controller.
![]() Note |
The Authentication/Authorization list created through Cisco Catalyst Center provisioning supports a maximum of 100 entries. Entries beyond 100 can be created, but they do not function. |

Feedback