The internal database can be used to configure the clients for MAC-based authentication. If derivation rules exist or if the client configuration in the internal database has a role assignment, these values take precedence over the default user role.Īuthentication server group that thecontrolleruses to validate the clients. You configure the default user role for MAC-based authentication in the AAA profile. (See Chapter 10, “Roles and Policies” for information on firewall policies to configure roles). The user role that will be assigned as the default role for the MAC-based authenticated clients. This chapter describes the following topics:īefore configuring MAC-based authentication, you must configure :
MAC-based authentication can also be used to authenticate Wi-Fi phones as an additional layer of security to prevent other devices from accessing the voice network using what is normally an insecure SSID. Clients may be required to authenticate themselves using other methods depending on the network privileges required. For example, if clients are allowed access to the network via station A, then one method of authenticating station A is MAC-based. MAC-based authentication is often used to authenticate and allow network access through certain devices while denying access to the rest. While not the most secure and scalable method, MAC-based authentication implicitly provides an addition layer of security authentication devices. Use MAC-based authentication to authenticate devices based on their physical media access control (MAC) address.
#AVIRA FOR MAC AUTHENTICATION HOW TO#
This chapter describes how to configure MAC-based authentication on the Arubacontrollerusing the WebUI.