Flexible Authentication Overview

Flexible authentication combines MAC authentication and IEEE 802.1X authentication as a single authentication procedure.

Note: Flexible authentication is not supported in private VLANs.

Note: The term "client" is used to indicate the user or device that is going through authentication.

In modern networks, a wide variety of client devices may attempt to connect and utilize network resources. Such networks cannot be left unrestricted due to security concerns. There must be a mechanism to enforce authentication of the clients before allowing access to the network. In addition, a single authentication method may not be universally compatible with all client types, especially when devices support different authentication protocols. Assigning separate ports for each authentication method is impractical and inefficient. IEEE 802.1X authentication and MAC authentication, and a combination of both, provide strong, yet flexible methods to validate the clients and prevent unauthorized clients from gaining access to the network. Once a client successfully authenticates, its MAC address is assigned to a VLAN specified by the RADIUS server. Additionally, any policies returned by the RADIUS server are applied to the client, ensuring appropriate access control and network segmentation.

RUCKUS ICX devices support the IEEE 802.1X standard for authenticating clients attached to data ports. Using IEEE 802.1X, you can configure an ICX device to grant or deny access to a port based on information supplied by a client to an authentication server.

When a user logs in to a network that uses IEEE 802.1X, the RUCKUS ICX device grants or denies access to network services after the user is authenticated by an authentication server. The user-based authentication in IEEE 802.1X provides an alternative to granting network access based on a user IP address, MAC address, or subnetwork.

MAC authentication is another mechanism by which incoming traffic originating from a specific MAC address is switched or forwarded by the device only if an authentication server successfully authenticates the source MAC address. The MAC address itself is used as the username and password for authentication; the user does not need to provide a specific username and password to gain access to the network. If authentication for the MAC address is successful, traffic from the MAC address is forwarded in hardware.

Flexible authentication provides a means to set the sequential order in which IEEE 802.1X authentication and MAC authentication methods need to be executed. If both authentication methods are enabled on the same port, by default, the authentication sequence is set to perform IEEE 802.1X authentication followed by MAC authentication. Both the IEEE 802.1X authentication and MAC authentication methods must be enabled at the global and interface levels on the same port to execute Flexible authentication. Flexible authentication facilitates multiple authentication methods to validate a client using a single configuration on the same port. Thus, different clients that support different types of authentication can be authenticated using a single configuration.

After successful authentication, different policies can be applied to restrict the way the client accesses network resources. VLAN policies, phone policies, and ACL policies can be enforced using VLAN assignment, ACL assignment, and phone-specific information to provide different levels of service to the client and to control the destination of the client.

The following table shows ICX features that have been tested for compatibility with various Network Access Control (NAC) applications.

Features Tested for Compatibility with Various NAC Applications

Feature Free RADIUS Aruba ClearPass RUCKUS Cloudpath Cisco ISE
IEEE 802.1X authentication Yes Yes Yes Yes
MAC authentication Yes Yes Yes Yes
Dynamic VLAN assignment Yes Yes Yes Yes
Dynamic ACL assignment Yes Yes Yes Yes
External web authentication Not applicable Yes Yes Yes (Release 2.1)
Change of Authorization (CoA) Yes Yes Yes Yes (Release 2.1)

Note: Refer to the RUCKUS FastIron Features and Standards Support Matrix for the list of supported platforms.