Sunday, February 9, 2014

iPad Safari access of a SharePoint 2010 Web Application

As a continuation of my previous blog post located here, I would like to explain further progress made in the investigation of accessing a SharePoint 2010 Web Application using the iPad Safari browser.

We have found that exposing a SharePoint 2010 Web Application using Claims based Authentication and turning on Integrated Windows Authentication does seem to improve the user experience significantly, in fact, it is pretty close to a seamless experience.

The reason I say "almost" is because the first time the site is brought up on Safari we experienced difficulty bringing up the site, but  upon doing the same  the second time ( we are still trying to research the exact reason), the site came up fine. The user experience is find after that, even after I cleared  cookies on the iPad.

I have to say, if you have no option but to Windows Authentication, then this is the best experience I have seen so far on iPad Safari. If you have other options, then using the ASP.NET Sql Membership and Role Providers will provide the best user experience on an iPad. And if you want to test the experience without doing putting any effort, simply create an Office 365 test account, and test the SharePoint Online site on iPad Safari.

Single Sign-on: Just like your on-premise SharePoint installation allows pass through for NTLM and Integrated Windows Authentication Sites, how would you turn on Single Sign-on on an iPad? If you organization uses some form of Mobile VPNsolution, that could be the answer. Or, The answer lies in your Corporate Identity Management strategy. Here ins potential solution: If your identity Management solution supports SAML, you could enable single-sign on by making the SharePoint 2010 Claims aware Web Application use that Identity Provider (IDP) as a trusted identity provider, as shown in the screenshot below:


(the names of the provider have been erased in the screenshot due to confidentiality reasons)

However, Mobility remains a challenge with SharePoint On-Premise installations, at least up until the SharePoint 2010 Release. I am not sure if the issues have been resolved for Windows Authentication Sites using the SharePoint 2013 Platform. Will be testing further and blogging my findings.

No comments: