When configuring an 802.1X-secured WLAN, RUCKUS systems such as SmartZone, RUCKUS One, or RUCKUS Cloud typically rely on an external RADIUS server for user authentication. However, in the event of a controller failure or connectivity loss to the RADIUS server, RUCKUS APs can continue to authenticate users locally if the local user database is enabled and configured.

The Local Authentication Database allows APs or controllers to store a limited set of credentials that can be used when external AAA services are unavailable. This ensures continued access and redundancy for critical WLANs without requiring external dependency. According to RUCKUS One Online Help -- WLAN Configuration and AAA Settings, enabling the Local Authentication Database provides fallback authentication for 802.1X clients during system or connectivity failures.

In contrast, the proxy and non-proxy modes define how authentication requests are relayed to the RADIUS server, while Dynamic PSK (DPSK) is a separate authentication method that replaces 802.1X with per-user keys.

RUCKUS One Online Help -- WLAN Configuration: AAA Authentication and Fallback Options

RUCKUS Analytics 3.5 User Guide -- Client Authentication and WLAN Events

Ruckus Cloud / RUCKUS AI Documentation -- Authentication Mode Descriptions