Depending on the client, once they have connected to an SSID using WPA3-SAE, they won't connect to WPA2-PSK. So, it's not recommended to mix authentication types on the same SSID.
What is wise in your situation is hard to tell; but I would keep the same setting everywhere.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Apr 27, 2026 05:31 AM
From: Notknown
Subject: Clients preferring the technically worse connection for higher Security?
Hello Airheads,
We have a Location, that is currently running Unifi APs and Aruba APs together, but on different floors of the building.
Both of them have their own Set of SSIDs, but we have two shared between them too.
for those two SSIDs, the Name itself is the same, they use the same Password and the same VLAN Assignment. the only difference between the two networks is, Unifi is set to WPA2 and Aruba to WPA3.
But: when a client that is on the Unifi floor tries to connect to the Wifi, it shows full signal strenth first (presumably to the Unifi APs), but after connecting, then only connects to the Aruba APs with a worse connection, since they now connect through two floors of the building.
is the WPA2/WPA3 difference really the reason why our Laptops refuse the Unifi APs or am i overlooking something else? (setting the Unifi's to WPA3 would be unfavorable since, in their area, we have some older clients that have problems with WPA3.)
-------------------------------------------