Everyone, and welcome back to the full video series, and today's lecture will have a high level overview
about active directly.
Now, I'm very sure that most of you have heard about active director because it is generally used in
most of the organizations, specifically the enterprises.
So let's look into the acting directly with the simple use case.
So let's look into the traditional way where you have an organization and within the organization,
you have different applications.
So let's assume this is a W.S. then you have application to and then you have an application three and
you're you have the users, which are part of the organization.
Now, if user wants to log into each of these applications, what would had to be done is that in each
and every application you would have to configure the users manually.
Like if you are using it, then you have to go to IAM, you have to create AMM users.
So if you have an application, do you again have to create manual users?
If every application three again, you have to create manual users away.
And if someone leaves the organization, you go to the interviews, you delete diam user, then you
go to the application.
Do you delete the Amusa there?
You go to the application, use it application three, you delete the user.
So if you see this is quite a bit pain and typically when you talk about enterprises, you would have
like 20, 30 users may be joining, maybe leaving the organization.
And for a system administrator doing this on a regular basis for 20, 30 users is a very big pain.
And this is the reason why there is a need for a central authentication.
So when you talk about a better way of what we basically have is you have a central server and what
you have is you create all the users in these central server and then you connect the central server
with all of the applications which are present within the organization.
And that's all the user have to do, is user just have to log in once and he can access all these services
or he can log into each of these services with the credentials we just stored in this central server.
So this central server can be active directly.
It can be other services as well, like identity management, which is provided by that.
It had.
So this central server is what we will call it, active directly.
Since this is an active direct reflector now, things becomes much more simpler because if you want
to remove the user, you can remove the user from the active directory itself.
You don't really have to go to each and every application and remove the user.
Same goes with adding the new user.
So when you talk about active directly, activity is one of the most popular directress service developed
by Microsoft.
Now the server running the active directress service is called as the domain controller, and it can
authenticate and authorize the users and computers which are associated with it.
So within the active directly on the left hand side, you see you have the users and within the users
you can have various users, which you can create and you can change the posture of the users from your
you can delete the user, you can add the user, et cetera, and then you can configure the users to
access each of these services, like if you want to use it.
One, two.
If you want to use one to only access the EAW, then you can configure the policies accordingly.
So this is a very high level overview about the active directly.
I hope you understood in a high level or you want what activity degree is and what are the things that
we can achieve.
The Help both active directorate.
So this is it about this later.
I hope this has been informative for you and I look forward to see you in the next.