Forum Discussion
Claims Authentication - STS
- Jan 13, 2017
If you use Windows based claims auth, the IP (Identity Provider) is Active Directory. If you use Forms Based auth, the IP is the form auth provider. (Don't use .Net Membership, use ASP.NET Identity. In both scenarios, the token consumed by SharePoint is from the SharePoint Claims Issuer.
SharePoint requires a SAML token. Last I checked, Facebook did not issue SAML tokens, so you need something in between that will do that. You can get SAML tokens from ADFS, Ping and a few others.
However, if you use an Identity Provider that is not active directory, you will have issues with the people picker in SharePoint. I've written about that here: SharePoint People Picker in Claims-mode Web Applications
If you use Windows based claims auth, the IP (Identity Provider) is Active Directory. If you use Forms Based auth, the IP is the form auth provider. (Don't use .Net Membership, use ASP.NET Identity. In both scenarios, the token consumed by SharePoint is from the SharePoint Claims Issuer.
SharePoint requires a SAML token. Last I checked, Facebook did not issue SAML tokens, so you need something in between that will do that. You can get SAML tokens from ADFS, Ping and a few others.
However, if you use an Identity Provider that is not active directory, you will have issues with the people picker in SharePoint. I've written about that here: SharePoint People Picker in Claims-mode Web Applications