I would not use internal database for WPA-Enterprise authentication as it will use PEAP-MSCHAPv2 which is deprecated and should not be used unless you have full control over your clients (supplicants).
If you ignore that, I would indeed think this may be a UI Bug if it can be configured on CLI but not on UI. It may be on purpose because of the above, but please reach out to Aruba Support and let them find out if this is on purpose, a known, or unknown UI defect.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
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: May 19, 2022 06:46 PM
From: Jay Seley
Subject: UI bug? Can't use internal RADIUS server with WPA3
I'm testing WPA3 in a lab with an IAP-315 running Instant 8.10.0. I noticed that when I select WPA2-Enterprise I have the option to use the internal RADIUS server:
But when I choose WPA3-Enterprise, I'm only allowed to choose external RADIUS servers (InternalServer is not available as an option):
------------------------------
Jay Seley
------------------------------