Captive network problem over https with IOS 11/High Sierra

Hi,


I've noticed that my Apple devices running ios 11 and Mac OS 10.13 High Sierra will disconnect their wifi connection immediately if the server responding with captive portal uses https. Our company's captive portal has the option to force end systems to use https for it, so if it receives an http request for a portal, it responds with a port 443 redirect request. This appears to be neglected by the new OS's captive network assistant which then, simply, drops the wifi connection completely.


In currently released iOS and Mac OS's, the wifi connection does not drop - it just simply won't display the portal when our redirection is issued. The new beta systems, though, just disconnect the wifi connection immediately. This is hugely problematic as there is no workaround for end systems other than for system administrators to disable the https requirement for the captive portal.


Is this a known issue and/or is there any workaround from an end-system perspective? I did not find any topic like this on the forums as of yet.



Thanks.

Up vote post of moooooog35 Down vote post of moooooog35
13k views
Posted by
moooooog35
Reply
Add a Comment

Replies

My company is having a similar issue with our captive guest wifi. The captive page appears but gives an error stating the web page could not load. We have no workaround right now and have already filed bug reports. This sounds like a much larger issue with the current betas. Hopefully this will be resolved in the next beta.

Posted by
groovesys
Up vote reply of groovesys Down vote reply of groovesys
Add a Comment

I had the same issue and found a solution

When connected to the Wifi, there is a check of the link: captiveapple.com

And as without the captive portail authentication there is no Internet access, the check failed. So wifi is disconnected.

I add this link to "pass" in my Firewall and now I can get the wifi connection. May be try

Posted by
mohachko
Up vote reply of mohachko Down vote reply of mohachko
Add a Comment

After weeks of troubleshooting we were able to resolve issue for all clients. After updating our Cisco code on the controller there are some seetings that get enabled by default that one in particular was the cause for our guests not being able to connect.


After we disabled 11K, all clients were able to successfully connect. I have a case open with Apple Enterprise support to have them isolate the cause for why we have to disable 11k to allow connection, because we don't want to keep 11k disabled due to advantages it offers for Apple and other smart WIFI clients.

Posted by
EclipseOK
Up vote reply of EclipseOK Down vote reply of EclipseOK
Add a Comment