We were recently tasked with provisioning a SharePoint 2013 farm that would authenticate users with SAML Claims and leverage ADFS 2.0 as the identity provider. Nobody on the team had experience with ADFS 2.0 going into this, but figured since customers have been using ADFS and SharePoint together for years that the process would be straight forward. Unfortunately we found that configuring SharePoint 2013 to use ADFS 2.0 as an authentication provider came with a series of usability issues dealing with areas such as Search, Office Web Apps, and the People Picker.
** You may also be interested in our updated SharePoint 2013 and ADFS 3.0 Installation guide.
This series of articles will cover our experience and hopefully provide insight to others as they embark on their own journey. Below is list of articles:
- SharePoint 2013 and ADFS 2.0 Installation Guide
- Lab Environment
- Install Windows Certificate Authority
- ADFS Prerequisites
- How to Install and Configure ADFS 2.0
- Configure User Profile Service for ADFS 2.0
- Configure Search to Crawl Web Applications Using Claims and ADFS 2.0
- Configure People Picker to resolve ADFS Identities
- Adding Host Name Site Collections to Existing Web Application Configured to use ADFS 2.0
- Validate Configuration with “Claims Viewer Web Part”