Consider the following scenario: You have one of the following User Profile Synchronization configurations for SharePoint: SharePoint 2010, which utilizes Forefront Identity Manager (FIM) for User Profile Synchronization. SharePoint 2013, using the “Use SharePoint Profile Synchronization” option, which also uses FIM. SharePoint 2016 or 2019, using the “Enable External Identity Manager” option, which (typically)

  When the SAML Identity Provider (ADFS, SiteMinder, Ping Federate, OKTA, etc) token-signing certificate is renewed or rolled over, SharePoint can be in trouble. This is because there’s currently no functionality in SharePoint to automatically update the certificate within the Trusted Identity Token Issuer on the SharePoint side when it’s been updated on the Identity

Consider the following scenario:   You break permission inheritance on a list and give some users permission to only that list. The users can browse to the list, but when they try to add an item to the list or edit an existing item, the following error occurs:   The server was unable to save

Update 3/14/23: This issue was fixed for SharePoint 2019 and SPSE in the January 2023 updates.  See below for details. Consider the following scenario: You have a SharePoint Server 2013, 2016, 2019, or Subscription Edition (SPSE) web application that has both Windows and Trusted Provider / SAML authentication (ADFS, etc) enabled. You have a list

I came across this topic troubleshooting a support case where users were getting Access Denied to a site using Trusted Provider (SAML) authentication. The Issue: Users were given permission to the site using a group that had other groups nested in it. The users were not direct members of the group being used for permission.

Disclaimer: The below is a summary of observations made as the result of some reverse-engineering and Source Code review. It’s not necessarily to be taken as “official,” but does check out according to my testing. This is post is not about configuring Forms-based Authentication (FBA). There’s plenty of other posts out there about that. The

This post is about how a simple web service failure, caused by a networking or Active Directory issue can take your site down. I’ve come across this a few different ways. The behavior is almost always intermittent, making it hard to track down.   Possible Symptoms: Users intermittently receive a “Something Went Wrong” message when