Welcome back, folks, this is Rauschenbusch, and this session is about understanding the authentication,
to be very precise, understanding the form based authentication.
So it would be pretty you pretty obvious that whenever you you want to get your access to any of your
accounts, your e-mails, any of your personal information, you have to log into some sort of application.
Right.
And that's where you have to put your email and submit your email password login antiperspirant on those
stuff.
So it is pretty a very regular task for you to make use of those credentials.
But this session will understand how exactly that works, how exactly the phone based authentication
works.
So I understand this, but this is not the only way of authentication before this.
There has been many, but this is something which is pretty successful.
And that's why we still see every every everywhere, in fact, everyone on the Internet.
All right.
So let's get started.
So what happened is a as an example, you have your user, you have your Web server and they database.
As of now, it's pretty clear that database is the purpose of databases to store the user information.
But in case of the authentication, the database would be having a separate table for storing the credentials.
Right.
And this would gatti's the information about individual users, that user name, their first name and
last name, the location.
What was the last time the in and what was what what is the current IP, what was their last IP address
and all those stuff.
Right.
These are dynamic.
What is static goes there bassma their name and location and all of this stuff.
Right.
So that's where you would see a database prison which will carry the user information.
You could see the detail about John Laws, Bob Charlie as well.
So this is something which is already being present in the database.
As of now, we only understand the purpose of Web server is to take care or handling the request and
the response, taking the request and giving it to the database, taking the request back from the database
and then then delivering it to the user as a part of response.
Right.
So that's what the purpose of Web server.
Now, for the user, it's always the there's always Web server.
Now, understand, what exactly happens is a user first sends the request.
The remember, this is nothing but the a kind of a stupid request.
But in case of especially in case of login authentication, when user click on the login problem he
has, he has to submit the credentials.
Right.
You see the login form, it will ask the user to submit the username and password and that is this will
become the EDP post.
If you are following me through the scores, you will understand this has to be a soon to be post because
that's where you upload, you submit some information and that's why it's supposed to be the post request.
Now, this information goes to the database and this has to go in a certain form because when the request
comes to the Web server now, Web server has to decide whether to let the let the user get into our
network or, you know, in the server or not for this the Web server quite easily Dabis to know whether
this is a valid user or not.
So this way is nothing but the escritoire.
All right.
So with the help of Esguerra, the Web server, trying to understand if this is a valid user or not.
Now, this is actually creating these will be having started forming in this form.
And basically, as what we have learned, the way we have deployed, we have created the individual
rules in the database as well.
Right.
So this is how exactly it looks like the Web server create and create and create a sort of security,
which is select data.
Any data from login login would be the name of this entire table and their user name is John.
And Password is random.
One, two, three, step.
So so this this query goes to the database and database.
I mean, then the query perform and the first ID says it verifies with this detail, it says that the
user name is John and the password is this, that this is absolutely correct.
And the request comes and comes back from the Web server and.
The website will get to know, OK, hey, listen, you are a valid user and now you are allowed to access
your resources or you're allowed to get into the website and enjoy it further.
So that's how the authentication really works.
Why we learned this is because when we start hacking the website, when we start hacking the Web application,
the purpose is to get into the system without even knowing the username and password.
I know this sounds crazy, but we'll make this happen.
And for this to understand, it is very, very important for you to understand how the authentication
really works.
What are the frisco's in the user name?
What goes in the password?
It's pretty obvious.
Very John goes into the user name and random one to three star will be there in the password.
This has to be submitted by the user, of course, but this is what will be exploiting it.
When will you try to get the access into the document?
All right.
I hope you got the idea.
We'll catch you in the next session and thinking.