We're also in the process of testing eduroam on our campus (and we also use Cloudpath) but we are using one certificate chain and in fact the exact same certificates for eduroam vs. our own WPI-Wireless. It sounds like you are using different certs/cert chain--is that the case? I'll try testing with Android today.
On Thu, May 08, 2014 at 02:00:01PM +0000, Turner, Ryan H wrote: > We are in the process of deploying eduroam across our campus. The SSID will > be deployed, concurrent with our current EAP-TLS SSID (UNC-Secure) around > Fall. Ultimately, UNC-Secure will go away, and only eduroam will remain. We > are onboarding with Cloudpath. In our initial testing, one of our android > users reported to be able to successfully connect to eduroam after > configuring, yet the configuration blew away their UNC-Secure setup. When > the user attempted to reonboard with UNC-Secure, he go the screenshot that is > attached. I have sent an email to cloudpath, hoping this is just an > oversight. There can't be many places running multiple EAP-TLS SSIDs > concurrently. > > Is this really a limitation with Android? Seems to work without any issue > with Windows, Apple, and iOS. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
