Group administrators:
Recent members:
eduroam client issues
TLDR; most client issues are solved by ensuring that the client is configured via a deployment tool
IOS9
Apple have changed the behaviour of IOS 9 with enterprise WiFi. It appears that if your organisation is using a certificate not natively known by the device then it will no longer accept just username/password entry and present you with a 'verify the server' option. it just silently quits.
This may be solved by ensuring the CA root is known to the IOS9 device... but if you are doing that, you may as well ensure you have a deployent tool to do this task for you - eg eduroamCAT, Cloudpath Xpress or SE, ClearPass etc
eg see http://pages.queens.ox.ac.uk/it/2015/09/17/apple-ios-9-breaks-eduroam/
if the device has a correct profile installed, it should work. This is actually good - its much better for security and ensures the device is correctly configured.
Admins note - IOS9 also requires a larger DH key - at least 1024 on the RADIUS server - please see other advisory. Future IOS releases will also use TLS 1.2 and so your RADIUS platform will need to be updated if it cannot do TLS 1.2 negotiation correctly (see other advisory)
alan
Comments
Hi, Alan
Thanks for your post, and the helpful link to David's blog post.
We're in the process of upgrading the certificate presented by our RADIUS servers, and have found the same issue.
However, our experience has been that this is no different from iOS 8 (or at least 8.4.1). iOS doesn't appear to recognise the Quo Vadis root CA, even though it should be in its certificate store (at least for wireless authentication). I'm assuming that that would be the case whichever (legitimate, commercially-supplied) certificate was used.
Best wishes,
Steve Holden
University of Brighton