Single Sign-On (SSO) is the most important feature to enable early in application development. Nobody wants to manage another password, especially across multiple environments. Allowing stakeholders to login with their existing credentials dramatically accelerates user acquisition and engagement when designing a world-class digital experience.
Sitecore has integrated with Azure Active Directory (and other authentication providers) for many years using tools available in the marketplace. It wasn’t until the introduction of Sitecore Identity in Sitecore 9.1 that the integration with Azure Active Directory came Out-Of-The-Box (OOTB).
“You can use Federated Authentication for front-end login (on a content delivery server), and we recommend you always use Sitecore Identity for all Sitecore (back-end) authentication.”
There are lots of helpful articles from the Sitecore community that provide detailed steps on how to configure the Content Management and Identity roles to use popular providers such as Azure Active Directory, Okta and others.
Instead, I plan to cover more of the front-end benefits of Single Sign-On and Sitecore Identity.
Over the next few posts, I’ll be covering some topics that are not discussed as frequently or in much detail. Since I work primarily with Azure, I’ll be focusing on Azure Active Directory as the provider of choice:
- Azure Active Directory for Developers
- Single Tenant Azure / Multi-tenant Sitecore – setting up users, groups and app registration for a Sitecore development team
- Securing Headless Sitecore using Vercel SSO
- Securing Sitecore Authoring sites