Himmat Singh Dulawat (4x Sitecore MVP)

In this blog post, I will explain how to integrate the Single Sign-On in Sitecore Content Hub. For this blog post, I am using an example of Azure Active Directory (Azure AD), which has been renamed to Microsoft Entra ID. Before setting up the SSO in Content Hub using Azure AD, you must create and configure an Azure application registration. Refer to the official Microsoft Azure documentation for the correct procedures and retrieve the following details: metadataLocation: The URL or path pointing to the XML metadata of a SAML/WsFederation service provider spEntityId: The entity ID of the service provider. Normally, it would be the DAM URL followed by AuthServices/ACS idpEntityId: The entity ID of the identity provider. This would be the place owned by your team, where you would like the users to authenticate themselves Once you have the above details, log in to the Sitecore Content Hub, and from the navigation menu b...

To start with any secured web application, the developer needs to work on the implementation of the authentication functionality. If any user needs to enter into multiple secured web application on the same domain in the .NET framework, he needs to log-in through each of those applications. Logging in a number of times can be avoided with Single Sign On (SSO) functionality. SSO is a functionality that allows to login once and accesses multiple web applications with the same credentials. For example – once the user enters a user name and password on Gmail, he will be able to access Google’s other web application like Google Plus, YouTube, Play store, etc., with same credentials without logging in again. HOW SSO WORKS: When a user runs a page in an application that requires user-based authentication, the application searches for a cookie (forms authentication cookie) in the HTTP request, if it does not find the cookie, it redirects the current page to the l...