Unable to connect to wireless network validating identity
Eduroam is another popular choice for educational organizations.
I know this post is really old, however, this is similar to my issue except that last week, any client could connect to my wireless network and this week they can not. The windows/android/iphone clients were able to connect with 802.1x verifying against a local, Aruba based database of one user name.
The open network redirects to a custom captive portal (using HTTPS and a normal certificate issued by a CA) where users signed up and provided payment information.
After payment is complete, users are enabled in the RADIUS database, and can then reconnect to the WPA2-Enterprise SSID to get online.
To avoid all this trouble, in the next iteration (i.e.
next year) I plan to offer to install the server certificate directly from the captive portal, so that users (mostly Windows users) won't have an issue logging into the secure network.
When you list root CAs from other organizations in the "CA_file", you permit them to masquerade as you, to authenticate your users, and to issue client certificates for EAP-TLS. It is easy enough to distribute certificates using GPOs. Baring that, do your own star certificate (that is signed by a Root CA), you could sign your RADIUS server's certificate with? b) Select WPA2-‐Enterprise in the Security type dropdown menu. Click Manually connects to a wireless network, then click next. Under Information for the wireless network you want to add a) Enter Middlebury College into the Network name field. Right click the Wireless Network Connection icon on the Taskbar. d) Check to select Start this connection automatically. c) Select AES in the Encryption type dropdown menu.
Search for unable to connect to wireless network validating identity:
In turn the signing certificate authority's public key will be distributed to clients, either through GPOs, Active Directory Certificate Services or it was included by Microsoft in the Trusted Root Certification Authority repository.