iOS 8 Safari not working with sites using Windows Authentication (again)

This is NOT FIXED FOR SAFARI. No one in our company can access share point from their IPads because they will not authenticate. I was able to fix our third party apps. Apple wants to be serious about the enterprise but couldn't test IOS 8 against Sharepoint?

Ok, sorry, I heard that in 8.1 it already works at least for Safari. How did you fix it in your app? Are you using NSURLSession or NSURLConnection or it works for you using latest AFNetworking?

We had same problem, but IOS 8.1. fixed most of the issues. Update to 8.1 and try.

See my reply from Oct 29th. For me they fixed what they screwed up in IOS 7 so I had to undo my fix for it to work. Don't know what Safari is doing.

We have been trying to troubleshoot this issue for some time. We have noticed that there are differences when we use LTE vs, WiFi. chrome mostly works, though there are times when chrome does a post it also failed witha 401, though reports back with an invalid verb on the page.

it almost seems like that safari is seen as multiple requests from different clients and the server is authenticating each request. That might make sense over LTE as provider might be switching the source port of the connection and the server might see it as a new connection.

If I setup my iphone as a hotspot via LTE and then connect the ipad to the iphones hotspot via wifi, the iPad acts as as its foes when connected to the internal LAN on WiFi. The iPhone using LTE has the Authentication issues. Swapping the hot spot around I get the reverse. iPad has issues and iPhone does not.

Scott<-

Re:"Sharepoint and Safari".

The interesting thing about people talking in this thread is that many have issues with Sharepoint and Safari. We have a new Sharepoint 2013 server ( On Windows 2012 R2) internally and our connections to it seem pretty flawless. The sites are using claims based authentication.

The sites that we have issues with are on IIS8 (windows Server 2012). All of our sites are windows NTLM authentication. Negotiate has been removed.

Chrome and Aromic Browsers mostly work, Safari kinda works on Local WiFi, though not really at all on LTE.

When you set the atomic browser to turn on the Google chrome mobilizer, the Atomic browser then starts to get 401 failures.

Just found the Reduce Data usage option in Chrome. turn it on and Chrome behaves just like Safari And continually prompts for password.

SCott<-

iOS 8.2 beta still same issue. And the issue is for sure in iOS network libraries, there is still open issue for it at Apple. You might see some better or worse behaviour depending on LTE/3G/Wifi, but the issue is still there and occurs on all type of connection more or less.

This is a good point. Our problems are only with Sharepoint but we are still running IIS 7.5 not IIS8 so I wonder what would happen with that? One would think Apple could have tested that, especially with their big enterprise push.

Sad that its not Fixed in 8.2. The interesting thing is that Chrome Mostly Works. When we Submit forms we get an Invalid Verb error back, though its not an Invalid Verb, its a 401 on the POST. Here is the real Interesting part. I Added a Cert to the Website and then accessed the same page to POST back and under SSL I don't get the Invalid Verb issue.

Safari on the Mac under OS X 10.10.1 also shows signs of the Authentication problem.

If Chrome is using the network Libraries as Safari, why does it work and Safari does not?

When I opened a Trouble Ticket (not a Bug Report) they replied with " Our engineers have reviewed your request and have determined that you are experiencing an issue for which there is no known workaround at this time."

I've Submitted a Bug report to Apple with lots of Logging and they have not replied.

FRUSTRATING

If they only let us Change the Default Browser to Chrome I could get my Salesforce back and running. I did come across this though, you can use URLs like this to force iOS to open in Chrome: googlechrome://<url> (i.e., googlechrome://www.google.com) googlechromes:// works too.

Scott<-

So I Submitted a Bug Report (19047616) on Nov 20th and last week I finally received a reply.

"Duplicate of 18460080 (Open)"

Though there is no way for me to check the status of 18460080 as it is not my Bug Report.

My Workaround for now was to create a new site for redirection in IIS for our iOS users that points to googlechromes://

The IIS Web binds to https://ios.site.domain.com

In the HTTP Redirect section it points to: googlechromes://site.domain.com$V$Q

Ticked 'Redirect all requests to exact destination (instead of relative to destination) '

Selected 'Permanent (301)'

From there the user can Click on a link from https://ios.site.domain.com/Path?parameters and it will pop safari, then open the link with path and parameters in Chrome.

This is really Sad.

Scott<-

Does anyone know if the new update to 8.1.2 would give any better result?

We're experiencing the same problems, and would love it for our SharePoint environment to work again with IOS 8+

We're using SharePoint 2010, on windows platform, with windows authentication.

Gr FB

freakb, I cannot speak to 8.1.2 as I have not installed it, though the first Beta of 8.2 did not fix the issue. They just released the second Beta of 8.2, though I have not installed that yet either.

My Last Correspondence with Apple said they were closing my Duplicate Bug Report. The status of the Duplicated Bug Report still shows as 'Open', so I'm guessing that its either not in the Beta 2 of 8.2 or they are waiting to the release of 8.2 to close the issue.

That said, our Sharepoint Sites are running Sharepoint 2013 with Claims Authentication. All of our Sharepoint sites work fine with iOS8. I believe it has to do with the Claims/Forms Authentication that they are using. I believe that you have the option to convert Sharepoint 2010 sites to use Claims Authentication. (I had to Convert my WSS3 sites to 2010, then the 2010 to claims auth, then to 2013) Maybe create a new Claims Auth Based site on your 2010 server and see how the Authentication works with iOS8 on it.

Still not fixed neither in iOS 8.1.2 nor in 8.2 Beta 2. I have suspicion that Apple just ignores this issue by mean or even worse it was implemented there by mean to make M$ stuff not working on Apple devices 😠

I understand your frustration BalkiX, but seriously, comments like this hurt your credibility. Today, Microsoft still = Enterprise computing. Saying Apple is intentionally crippling the ability of Microsoft products to work with iOS devices is absurd. First, because it means you've missed or ignored the fact that more recent versions of Sharepoint and other Microsoft services do actually work with iOS 8 and second, if you pay any attention at all you already know Enterprise is a huge focus for Apple.

Maybe Apple are abandoning old compatibility. Or maybe this is just lower on the priority list. Who knows. But it certainly is not intentionally crippling Microsoft products.

It's not just about Sharepoint. Even the windows authentication doesn't work (and client side certificates), which is bigger issue for me. Mainly if you develop iOS application that needs to connect to IIS server using this type of authentication cause your customer demands it. And if this doesn't work and you can loose million $ contract then you would be also pretty frustrated.