Integrate Countersign Authentication with airSlate SignNow

Integrate countersign authentication

[Music] this is a presentation of one login training welcome to configuring windows domain authentication also known as desktop single sign-on this is the first of three videos in this series the purpose of this course is to take an in-depth look at configuring windows domain authentication so let's take a look at what we'll be covering in our first video we're going to start off with a basic overview of the feature and how it works and do a quick refresher on installing the active directory connector which is the key component that needs to be in place for windows domain authentication to work in the second video we'll look at the main configuration steps necessary to put windows domain off into place and in our final video we'll look at how to configure windows domain authentication for load balancing and cover a few troubleshooting tips first let's take a look at what exactly windows domain authentication is let's answer a few basic questions first what is windows domain authentication which is also known as wda or desktop single sign-on and desktop sso there was a recent name change from desktop sso so it's always good to know previous names and current names then we'll take a look at how wda works then how it affects a user's experience finally we want to compare it to another one login product one login desktop that actually gives the end user a very similar experience when they log into the one login portal so it's easy to get one login desktop and windows domain authentication confused was even easier to get them confused when wda was referred to as desktop single sign-on so first simply put wda allows users to log into the one login portal from their windows domain joined workstations without having to provide a username and password the key is to understand that it can only be enabled through active directory directory services configuration with one login so each active directory configuration can be configured to sync all users from within a particular active directory forest if you want to enable it for users from multiple forests you'll have to configure a two-way transitive trust between the active directory force finally you can configure the authentication request to be load balanced between our active directory connector instances again these are the installations of the software that we use to sync with active directory and you can install these on more than one server therefore you can load balance this process between those servers here we're seeing one login admin ui and in this particular account we actually have two active directory connectors configured only one of these connectors like the one i'm pointing to with that arrow can be configured to handle this windows domain authentication process so how does windows domain authentication work well the basic off flow looks like this a user is logged into their domain joined workstation and they open a browser and navigate...