Now, here we will look at the Linux account authentication, what what does it really mean is that
you create local accounts right on your local computer?
In this case, we have our Linux machine.
We create an account.
We just learned that.
Right.
So what if you have the thousands of users?
So then.
How can you manage all those users, how can you change your password, so then that's the problem comes
in when you have to actually add multiple users to, of course, multiple servers as well.
So what will happen if a user joins a company and or a system administrator or a new user joins a company
and you have to create his or her account to, let's say, a thousand servers?
Now, are you going to log into every server and create a user account?
Well, that's not efficient.
And usually the companies don't work that way and they don't actually create user accounts individually
to etc..
So what they do is in Windows environment, they add some kind of directory service or directory server
where user could login, having the authentication through a different server.
So how it works.
Let's see what type of accounts there are.
So there are basically two types of accounts that you have, one account that is sitting local to your
machine, meaning that you create a user account and Linux machine by running a command user add and
then you add it to the group or give permissions and so on.
So most of the Linux accounts be created locally.
And the reason we create most of the Linux accounts is because Linux is not like a user environment
where you have a log in and perform different tasks.
It is basically used for system administration purposes or for to run major applications anyway.
So if you need to create a local user account, we already learned that.
Now the question comes in, what if you have to create a user account of 10000 different servers, then
you have to have a domain or a directory account on a server.
So how it works is you have all users account under one database.
So look at this picture.
So you have a client, which is a server, which is your Linux machine, any machine that you have installed.
And then you have another server, which is in our case, we call it a directory server.
So a directory server as user, try to log in to the client and into account authentication goes against
the server.
So the server checks to see if that account exists and if the account exists, it will reply back,
saying the user has been authenticated and it's OK for user to go ahead and log in.
And that's how and a user that is created on the directory structure will log in.
Now, remember, this is not for those users that are created locally.
This is this authentication process only works with the client and the server.
So there is a sober out there in windows.
There's a directorate that gets authenticated, comes back, and that's how you get it authenticated.
So in Windows now, Windows has this product active directory, which is called Microsoft to directly,
which is awesome product.
It works so good.
It works so efficiently for the users.
So how how it works is you go into the windows, acted rectories server, you create an account on the
actor directly and then it gets authenticated and then you can log in to the client.
So now remember how this works.
This goes into the server and what protocol is uses.
If you need to log into a server, what protocol you use, you use SSL, right?
So if you want to log into the server using active directory or some kind of a directory service, you
will use a protocol called El LDAP.
So the question is Linux.
Does Linux users end up?
Now, remember one thing, guys.
Eldership is a it's it's a protocol.
It's not a directory that you get authenticated for Linux users.
A lot of people have this misconception.
So please clear that misconception that Al LDAP is not used for Linux LDAP.
That is just a protocol that is used for Windows, for Linux or any server or any even Mac.
They use this protocol to authenticate against a directory.
So what does hold up is so why a lot of people say, well, LWR, Zelda, Linux, well, that's not
a real case.
So in my next lesson, I will tell you exactly the difference between Helda actor actory and all other
different directress servers that are out there that you could use for Linux authentication or even
for Windows indication.
Not necessarily.
Windows needs to use active directory.
There are other products people use.
So active direct is native to Windows.
That's what people use it in most mostly use in a corporate environment, but in Linnik.
I'm telling you again, there is no such thing called eLab, and people say, hey, go ahead, use Helda,
no elde again, it's a protocol.
You can look it up.
It's called Light Weight Directory Assistance Protocol or direct something porchlight.
You can look it up.
So anyway, so that's a protocol that is used.
So I'll go over to the next lesson and I'll explain to you the difference between every Dirk disservices.