iOS 7 breaks windows authentication.

I don't think so. We did some tests here creating a new simple project that renders 100% HTML5 and still don't work. If you enable anonymous on the web.config it will work. Another tests was using an old MVC3 application rendering old HTML and the result was the same. The only thing that made it render correctly was enabling anonymous for the entire site.

So far, the only workaround that worked was enabling the private browser.

We still haven't figured it out what exactly is causing the issue on the normal browsing because the Safari is clearly authenticating.

What I noticed though is that the authentication only occurs once. It automatically saves the certificate and the user login and that's it. Every time we tried to access, we had to clear the cache. Maybe is something related to local storage/cookies.

We also thought that was an issue with the SSL, we turned it off and still didn't work. So...let's keep trying lol...xD

There is a discussion thread at Stack Overflow about this very issue. One solution that apparently works is adding an intermediate certificate to the IIS configuration. I'm not sure if this works with self-signed certificates (which is what we use) or what's involved. I haven't had a chance to try it.

http://stackoverflow.com/questions/18756241/receiving-ssl-error-in-ios7-gm-addtr ust-external-ca-root-is-not-trusted

I ran iOS7 Beta for 6 months and this was not an issue utill I upgraded to the gold-standard release. Very bloody annoying.

I'm not so sure the problem is NTLM because you are able to login. In theory at least this can't be the issue because the login should be handled by the server not the client. The client just hands in the details from the form.

If however there is something in the way that the page has been developed it could be that the iOS 7 version of Safari is less tolerant of the crap that MS has pushed with their IIS platform and ASP pages.

One test you could try is downloading the latest version of Webkit and see if that has the same issues. That's generally a later version of Safari.

Logging into one of our IIS servers using http works fine. It's only with https. It doesn't matter if it's IIS 6 or 7. Is this a certificate issue? We use self-signed certificates but are people seeing this problem with legitimate certificates too? I'm finding the same problem with Chrome. The Puffin browser is real nice, logs in fast with no problems but unfortunately it doesn't scroll allow some functionality with our application. Safari in private mode is the current workaround.

Darryn Lowe wrote:

I'm not so sure the problem is NTLM because you are able to login. In theory at least this can't be the issue because the login should be handled by the server not the client. The client just hands in the details from the form.

If however there is something in the way that the page has been developed it could be that the iOS 7 version of Safari is less tolerant of the crap that MS has pushed with their IIS platform and ASP pages.

One test you could try is downloading the latest version of Webkit and see if that has the same issues. That's generally a later version of Safari.

I don't think it has anything to do with content.

1) The sites load and render OK using Safari in private mode.

2) The sites load and render OK using Chrome on iOS 7. My understanding is that the iOS Chrome uses the same rendering engine (WebKit) as Safari - the one that is built into iOS 7 - the only rendering engine Apple will allow. (Gee, everyone screamed when MS built a rendering engine into Windows...)

3) Other reports on here say the sites load and render OK using Puffin, and I believe #2 also applies to Puffin.

This leads me to believe that it it the shell around the WebKit engine (i.e. Safari) since a different shell (Chrome, Puffin) works.

Ralph Nudo wrote:

Logging into one of our IIS servers using http works fine. It's only with https. It doesn't matter if it's IIS 6 or 7. Is this a certificate issue? We use self-signed certificates but are people seeing this problem with legitimate certificates too? I'm finding the same problem with Chrome. The Puffin browser is real nice, logs in fast with no problems but unfortunately it doesn't scroll allow some functionality with our application. Safari in private mode is the current workaround.

We see something different. We use https, but it works just fine with Chrome on iOS 7.

However, I do think you are correct that it is only https sites, and could have something to do with certificates and the way Safari is handling them.

Put your Safari browser into private mode and it will work. Did for us anyway.

Message was edited by: MorrisMcD

This works as a workaround, thank you very much Rey.🙂

I am still hoping Apple will issue a fix for this soon though, because we can't go around and tell 100's if not thousands of visitors to do this every time.

The shell should have no impact on the rendering because the "rendering engine" - WebKit - does the work of rendering the page.

However, I suspect the real issue is actually not the rendering engine but the Javascript engine as Chrome and Safari use two different Javascript processors.

Darryn Lowe wrote:

The shell should have no impact on the rendering because the "rendering engine" - WebKit - does the work of rendering the page.

However, I suspect the real issue is actually not the rendering engine but the Javascript engine as Chrome and Safari use two different Javascript processors.

Could be... the sites authenitcate and render just fine in iOS7 Safari with private mode enabled. So it would appear to me to be related to whatever part of Safari that is acting differently when private mode is enabled vs. not. Whether that is WebKit, Javascript, or the shell... don't know for sure. Of the three, I would put WebKit as last since it renders OK with private mode enabled in Safari and in Chrome in all cases.

Actually I was not aware (or nevery really thought about it) that Chrome used a different javascript processor - you maybe right and that's certainly a possible culprit.

This is the second ntlm has broken in iOS, the same thing happened in version 4.3. Strange that critical things like these slip through testing considering the amount of Windows authenticated enterprise websites out there.

Hopefully we'll get a patch soon.

NTLM authentication is handled in a seperate component in the browser, not in Javascript.

I'm having the same issue - and it looks like the issue persists in iOS 7.0.2, just released within the last hour.

I just did the upgrade to iOS 7.0.2. Unfortunately, the update did NOT resolve this issue.

😠