Hey Paul,
Thanks for taking a look at this.
With out situation, we re-issued the root CA key (eduroam was updated almost right after).
We were using the latest (at the time, almost a week or 2 now so perhaps there was a more recent update) and also tested removing the app and re-installing the app.
Here is what we did on one phone to try and get it working (it did not work):
-
Forget the eduroam SSID
-
Download the geteduroam app (using a different SSID)
-
Find our profile and install (enter username and password, etc)
We did vary this on a few devices (not forgetting the SSID, etc), but the process was fairly straightforward, however in all cases we could not get them connected.
Thanks,
Dan
|
Notice: This is external email. Verify the sender and use caution with any content.
|
Hi,
We tested the migration of CAs and simulaneous use of different CAs, and that worked well on iOS (among others), so it's not an issue I recognize.
I'll see what I can find/reproduce. Can you confirm you're on the latest geteduroam iOS update? (Does it work if you deinstall the App and reinstall?)
Regards,
Paul
On 17/04/2024 16:32, Daniel Sheppard (via geteduroam Mailing List) wrote:
Hello,
We recently changed the root certificate used to sign our EAP server certificate and we are having an issue with iPhone devices and the geteduroam app.
What I know so far
-
Android works no problem, both on a clean device and a previously configured device
-
iOS works on a clean device
-
iOS does not work on a previously configured device
-
The “cat.eduroam.org” profile manually installed on an iOS device works without any problem
-
Manually connecting works without any problem
The profile itself looks good. The static and live tests pass in the eduroam admin, but on a previously configured iOS device we always get a “Cannot connect to network” message.
We use Cisco ISE as our NAC and it reports a TLS error during the negotiating with the client device.
Anyone else experience this?
Thanks,
---
Dan Sheppard