iOS 7 breaks windows authentication.

I have several sites built on IIS 7 w/ telerik controls and use windows authentication. Chrome will authenticate but the telerik controls are non functional. We've had to tell users to use Puffin

I'm trying to deploy my new web app, yesterday me and my colleagues performed the update on iOS 7 for our iPhones and iPads. The web app works fine for the safari on iPhone, however, on the iPad, they are not working at all. I've been looking into the developer tools and sometimes the safari not even performs a GET on the server. I have to clear the cache and the browser history and then it reaches the server but still, it does not render the content. Through the inspect elements, the content is there (or partially there).

The weird thing is that one of the guys here didn't update his iPad and the safari can't load the web app either. Any clues??

It seems to be an issue with the NTLM authentication...any solutions??

Googling around today, I'm not finding much on this issue other than this thread, and a thread by a blogger a week ago saying he reported the issue to Apple. I am surprised this problem isn't being more widely reported, unless people simply haven't started upgrading their phones/ipads yet.

n4nd0, you have the same exact issue I'm going through all morning. I have this working on iPhone 5 with iOS 7 though.

What I am getting is two prompts on the iPad and then the "freezing" issue where the page is stuck loading with no content available.

One thing that will work will be to append the domain to the username. For instance:

domain\username

That works for iPhone, but not iPad. Seems really strange to me. Hopefully this is resolved or maybe there will be a workaround on IIS?

A work around that seems to be working for us (although not ideal) is to put Safari in Private browsing mode. We can now get to our Intranet page that is secured with Windows Authentication. I hope this helps others.

Intranet page is Classic ASP and running on IIS6.

Thanks for the work around, however it didn't work with us.

we using .net 4.0 and running on iis7

A work around that seems to be working for us (although not ideal) is to put Safari in Private browsing mode. We can now get to our Intranet page that is secured with Windows Authentication. I hope this helps others

Many thanks, that seems to work.

If you have already entered your credentials in standard mode, you may need to close/shutdown safari and then re-try in Private mode.

Thank you ReyAhtbor. We have a number of sites hosted on IIS6 & 7 using Windows Authentication. Your workaround works. As noted by others you'll need to close and kill off Safari before launching it and putting it in Private Browsing mode if you've attempted to login using normal browsing mode. Hopefully Apple fixes this soon.

Private browing mode works for me. Still in my case, it's difficult to go around and tell everybody with iOS 7 to use Private browing mode to use the site. I hope Apple will have a better solution to this issue.

Alternative browsers do work (Puffin, Chrome) - unfortunately, when an app needs to open a url in a browser, it goes to Safari. Apple won't allow you to specify your default browser.

Thanks to ReyAhtbor, Private mode is working for me.

Yes, private mode works for me also - but I only consider it a workaround, not a solution.

Unfortunately, there are side effects of private mode. I no longer have any browsing history, and no cookies means some sites may not work, or I will now have to log into them every time.

Although this is for Safari on a Mac, I believe it applies to iOS also:

Safari 6 (OS X Mountain Lion): Browse privately

http://support.apple.com/kb/PH11882

You can prevent others from gaining access to information about websites you visit by turning on Private Browsing. If you do this, Safari stops storing your browsing history, your website passwords, and cookies and other information for websites you visit.

We have the same issue but I don't think it has to do with the authentication. We tested the mobile side and we are allowed to authenticate. I actually beklieve this is related tot he coding on the website. Maybe iOS7 can not translate older versions of HTML. Is this the case?