I am trying to work out an SSO solution for a customer of mine who is using SharePoint online with Office 365.
I have the following test environment:
- Domain Server (+ certificate services)
- ADFS Server
- ADFS Proxy Server (non domain joined)
- Server for testing (IE+Firefox+Chrome installed)
- Web server for sample application
The ADFS server is federated with Office 365.
The SharePoint online website is (name changed) A.sharepoint.com
The internal domain's (Windows) DNS name is corp.B.com. (B is not the same as A in the SharePoint.com domain, is this an issue?)
The domain (internet) used for Office 365 is B.com.
An UPN suffix was created and is used on the accounts of corp.B.com to allow logging in as user@B.com.
The ADFS solution is working just fine (go to SharePoint Online or Office 365, get prompted for credentials, type UPN, get redirected to ADFS and auto-logged in).
What I'm trying to do is to use SharePoint auto-acceleration to bypass that login prompt, however after enabling the SharePoint acceleration on A-admin.sharepoint.com as suggested and enabling it for the domain B.com, nothing changed; still the same login prompt and no auto-acceleration.
I'm clueless as how to debug this or where to look any further.
Edit: Smart links are not an option, I'm looking at getting this working cleanly and not for an ADFS 2 solution but for something forward compatible and supported.
Best Answer
The issue is that the domain that was required for the SignInAccelerationDomain wasn't the domain used as the UPN for office 365 but the full domain name of the Windows domain. So i had to enable in my example the acceleration for "corp.B.com" and not for "B.com".