Cc Initials Authentication with airSlate SignNow

Cc initials authentication

[MUSIC] Corissa Koopmans: Welcome back to the Azure AD Architecture Deep Dive Series. We get a lot of questions about how Azure AD works under the hood, which we will share with you throughout this architecture series. Ramiro, I have customers who are starting to move to the cloud and want to know how Password Hash Sync authentication works. Can you walk us through that flow? Ramiro Calderon: Sure. Remember the last video we saw the actual synchronization of the hash on-premises domain? We have it here on this slide just for us to remember. So, that was the first use case. Now, let’s see how it works for authentication, which is the second use case. So, let’s start with Kim here. She’s our user. And let’s say that she wants to go to Salesforce, which is configured to use Azure Active Directory for single sign-on, but she hasn’t authenticated to anything yet. So, in that case, Salesforce will say, I don’t know who you are. Go to Azure AD and then Salesforce will redirect the user to Azure AD. Azure AD needs to know first how to authenticate Kim. So, it renders a login page where she can type in her user name, which is what we call an identity lingo, the user principal name or UPN. This is where this diagram starts. Azure AD has a lot of services under the covers that supply services for the different scenarios and today, we have this blue box here, which happens to be the authentication service. This service implements the different authentication protocols and provides credential gathering and credential validation experience for the end user. So, let’s start with step number one. Kim here types her UPN; let’s say it is Kim@Contoso.com and submits the form to Azure AD. This step right here is what we call Home Realm Discovery (HRD) because it’s Azure AD the way they discover what tenant the user belongs to. With that UPN Kim typed in, the authentication service then queries this core store to find out how she should authenticate with the system here in step number two. In this case, the core store will tell the authentication service that Kim is using the hash that’s stored in the cloud. This is determined by the domain configuration. The domain in this case is @contoso.com. Corissa: This means that all users in contoso.com will use PHS, right? What if my customers are not ready to move all users of the domain at one time and would like to test with a few users first? Ramiro: Well, that’s a very fair point, Corissa. We recently announced a feature called stage rollout, which will allow administrators to onboard a subset of users in the domain to use this configuration. So, the way it works is that here in the HRD stage in step number two, the system will reply with a specific configuration for Kim rather than the configuration of the entire domain. So, in step three...