Skip to Content

IdentityServer4 - WS-Federation and SharePoint

SharePoint is a document collaboration platform from Microsoft, capable of running multiple web apps. It also comes with support with other Microsoft products. But what if you want to use it with non-Active Directory accounts?

Deprecated

This article is now no longer up-to-date. Please click here to read the latest version

Oct. 14, 2022

Added deprecated box. 

This article is being revised, please visit: https://www.scottbrady91.com/Identity-Server/IdentityServer-4-SharePoint-Integration-using-WS-Federation

SharePoint is a popular document collaboration platform from Microsoft, capable of running multiple web applications which in turn consist of multiple web sites. SharePoint also comes with of the box support with other Microsoft products such as Office 365 and Active Directory.

But what if you want to use SharePoint with non-Active Directory accounts? Or have SSO across all of your applications, even on mobile devices? Even Azure AD B2C struggles with this, due to it’s lack of support for SAML 1.1 tokens. This is where traditional identity providers start to struggle and IdentityServer steps in.

IdentityServer 4 is an authentication framework capable of out of the box Single Sign On (SSO) and security for your APIs, and most recently support for implementing your own authentication protocols and tokens, with a sample implementation for the WS-Federation protocol and SAML tokens. SSO works across all applications regardless of whether they are using OpenID Connect or WS-Federation.

This article will look at how we can integrate IdentityServer as a Trusted Identity Token Issuer for SharePoint.

Trusted Identity Token Issuer

Last updated: October 14, 2022

  • Hawkins Inc
  • Repower
  • Bosch
  • RandA
  • Plymouth NHS
  • American Heart Association
  • Systopia
  • Deliotte

We are proud to be a Certified B Corporation, meeting the highest standards of social and environmental impact.

Find Out More

Awards & Certifications