Comment configurer WPA2-Enterprise sur les plateformes de points d'accès courants (Cisco, Aruba, Ubiquiti)

How to Configure WPA2-Enterprise on Common Access Point Platforms — Cisco, Aruba, and Ubiquiti A Purple WiFi Intelligence Briefing [INTRO — approximately 1 minute] Welcome to the Purple WiFi Intelligence Series. I'm your host, and today we're cutting straight to the point on one of the most frequently requested topics from our enterprise clients: how to configure WPA2-Enterprise across the three most widely deployed access point platforms — Cisco, Aruba, and Ubiquiti. Whether you're the IT director at a 500-room hotel group, the network architect for a national retail chain, or the CTO of a conference centre operator, this briefing is for you. We're not going to cover theory for its own sake. We're going to walk through what you need to know to make a deployment decision, execute it correctly, and avoid the pitfalls that trip up even experienced teams. Let's get into it. [TECHNICAL DEEP-DIVE — approximately 5 minutes] First, a quick level-set on what WPA2-Enterprise actually is, because there's still a surprising amount of confusion in the market between WPA2-Personal and WPA2-Enterprise — and the distinction matters enormously for compliance and risk posture. WPA2-Personal — the version most people are familiar with — uses a single pre-shared key. Everyone on the network uses the same password. That's fine for a home network. It is categorically not acceptable for a business environment where you need per-user authentication, audit trails, and the ability to revoke access instantly. WPA2-Enterprise, defined under IEEE 802.1X, replaces that shared key with an individual authentication exchange. Each user or device presents its own credentials — whether that's a username and password, a digital certificate, or a token — and those credentials are validated by a RADIUS server before network access is granted. The access point itself never sees the credentials. It acts purely as an authenticator, passing the EAP — Extensible Authentication Protocol — exchange between the client and the RADIUS server. This is a fundamentally more secure architecture, and it's the baseline requirement for PCI DSS compliance in any environment that handles payment card data, as well as being strongly recommended under GDPR for organisations processing personal data over wireless networks. Now, let's talk about the three platforms. Starting with Cisco. Cisco's enterprise WiFi portfolio — primarily the Catalyst and Meraki lines — is the incumbent choice for large-scale deployments. Cisco DNA Center provides centralised policy management, and the Meraki dashboard offers cloud-managed simplicity for distributed estates. To configure WPA2-Enterprise on a Cisco Catalyst access point, you'll work through the WLC — Wireless LAN Controller — or DNA Center. The key steps are: define your RADIUS server under Security, then AAA, then RADIUS Authentication Servers; create a new WLAN profile; set the security policy to WPA2 with 802.1X as the key management method; and bind the RADIUS server to that WLAN. One critical point on Cisco: ensure you're configuring RADIUS accounting as well as authentication. Accounting gives you the per-session audit trail that compliance frameworks require. On Meraki, the process is even more straightforward — navigate to Wireless, then SSIDs, select your target SSID, set security to WPA2-Enterprise with my RADIUS server, and enter your RADIUS server IP, port — typically 1812 for authentication and 1813 for accounting — and shared secret. Meraki also supports RADIUS testing directly from the dashboard, which is invaluable during commissioning. Moving to Aruba. Aruba Networks, now part of HPE, is the dominant choice in hospitality and higher education. Aruba Central provides cloud management, and ArubaOS is the underlying platform. On Aruba, WPA2-Enterprise configuration lives within the SSID profile. You'll define an AAA profile that references your RADIUS server, then attach that AAA profile to your virtual AP profile. Aruba's ClearPass Policy Manager is worth a specific mention here — it's Aruba's own RADIUS and policy engine, and it adds significant capability around device profiling, role-based access control, and guest onboarding. If you're running a mixed environment with staff, contractors, and guests all connecting to the same infrastructure, ClearPass gives you the policy granularity to segment them appropriately. For a hotel deploying WPA2-Enterprise on staff and back-of-house networks while running a separate guest WiFi solution through a platform like Purple, Aruba's SSID segmentation combined with ClearPass for staff authentication is a very clean architecture. Now Ubiquiti. Ubiquiti's UniFi platform has gained significant traction in the SMB and mid-market space — and increasingly in boutique hospitality and retail — because of its competitive price point and genuinely capable management interface. UniFi Network Controller is where you'll do the heavy lifting. To configure WPA2-Enterprise on UniFi, navigate to Settings, then WiFi, create or edit your SSID, set security to WPA2 Enterprise, and configure your RADIUS profile — again, IP address, authentication port 1812, accounting port 1813, and shared secret. One important consideration with Ubiquiti: it does not ship with a built-in RADIUS server in the same way that some enterprise platforms do. You'll need an external RADIUS server — whether that's Windows Server NPS, FreeRADIUS, or a cloud RADIUS service. This is not a limitation per se, but it's a dependency that needs to be planned for. For smaller deployments, the UniFi Network Application does include a basic RADIUS server, but for production environments I'd always recommend a dedicated RADIUS instance. Across all three platforms, the EAP method selection deserves attention. PEAP with MSCHAPv2 is the most widely deployed method because it works with Active Directory credentials without requiring client-side certificates. EAP-TLS is more secure — it uses mutual certificate authentication — but it requires a PKI infrastructure and certificate deployment to every client device, which adds operational overhead. For most enterprise deployments, PEAP-MSCHAPv2 with a properly configured RADIUS server and certificate validation on the client side is the right balance of security and operational manageability. [IMPLEMENTATION RECOMMENDATIONS AND PITFALLS — approximately 2 minutes] Now let me give you the three most common failure modes I see in WPA2-Enterprise deployments, and how to avoid them. Number one: RADIUS server availability. Your RADIUS server is now in the critical path for every wireless authentication. If it goes down, nobody can connect. This means you need RADIUS redundancy — at minimum a primary and secondary RADIUS server configured on every access point. Most platforms support this natively. On Cisco, you can configure RADIUS server groups with failover. On Aruba, the AAA profile supports multiple RADIUS servers with configurable retry and timeout values. On Ubiquiti, you can specify a secondary RADIUS server in the RADIUS profile. Do not skip this step. Number two: certificate validation. A shockingly high proportion of deployments I review have client devices configured to accept any RADIUS server certificate. This completely undermines the security model — it opens you up to evil twin attacks where a rogue access point impersonates your network and harvests credentials. Configure your RADIUS server certificate from a trusted CA, and configure your client supplicants to validate that certificate. On Windows, this is done through Group Policy. On iOS and Android, it's handled through MDM profiles. This is non-negotiable for any environment handling sensitive data. Number three: VLAN assignment. WPA2-Enterprise enables dynamic VLAN assignment — the RADIUS server can return a VLAN attribute in the Access-Accept message, placing each authenticated user into the appropriate network segment based on their identity or role. This is one of the most powerful features of the 802.1X architecture, and it's frequently left unconfigured. If you're running a venue with staff, management, and IoT devices all on the same physical infrastructure, dynamic VLAN assignment is how you enforce network segmentation without managing multiple SSIDs. On the Purple integration side: if you're deploying WPA2-Enterprise for your staff and operational networks, and running Purple's guest WiFi platform for visitor connectivity, these two systems coexist cleanly. Purple handles the guest authentication, data capture, and analytics layer — including the WiFi analytics and footfall intelligence that venue operators use for operational decisions — while your WPA2-Enterprise infrastructure secures the corporate network. The key is clean SSID and VLAN separation at the access point level, which all three platforms support. [RAPID-FIRE Q&A — approximately 1 minute] Let me run through a few questions that come up regularly. Can I run WPA2-Enterprise and a guest network on the same access points? Yes, absolutely. All three platforms support multiple SSIDs per radio, each with independent security policies. Your corporate SSID runs WPA2-Enterprise; your guest SSID can run through Purple's captive portal with appropriate isolation. Do I need to replace my existing access points to deploy WPA2-Enterprise? Almost certainly not. WPA2-Enterprise has been supported on enterprise-grade access points for well over a decade. If your hardware is less than eight years old and running current firmware, it will support 802.1X. What's the difference between WPA2-Enterprise and WPA3-Enterprise? WPA3-Enterprise adds 192-bit security mode using Suite B cryptography, which is relevant for government and defence environments. For most commercial deployments, WPA2-Enterprise with strong EAP methods remains the standard. WPA3 transition is worth planning for new deployments, but it's not an urgent migration for most organisations. Is cloud RADIUS a viable option? Yes, and increasingly so. Services like Cisco ISE in the cloud, Aruba ClearPass as a service, or third-party options like JumpCloud and Foxpass provide RADIUS as a managed service, which removes the infrastructure overhead. For distributed estates — think a retail chain with 200 locations — cloud RADIUS can significantly reduce operational complexity. [SUMMARY AND NEXT STEPS — approximately 1 minute] To wrap up: WPA2-Enterprise is the non-negotiable baseline for any enterprise wireless deployment. The configuration process across Cisco, Aruba, and Ubiquiti follows the same fundamental pattern — define your RADIUS server, create your SSID with 802.1X key management, select your EAP method, and test before you go live. The differences are in the management interfaces and the ecosystem tools around each platform. The three things to get right: RADIUS redundancy, certificate validation on clients, and dynamic VLAN assignment. Get those three right and you have a solid, compliant, auditable wireless security posture. For your next steps: if you're evaluating platforms, use the vendor comparison framework in the accompanying guide. If you're ready to deploy, the step-by-step configuration walkthroughs for each platform are in the implementation section. And if you're thinking about how guest WiFi fits alongside your enterprise network, the Purple platform documentation covers the integration architecture in detail. Thanks for listening. I'll see you in the next briefing.