Session And Cookies
Session And Cookies. Facebook, Gmail, Twitter, we all use these websites every day. One common thing among them is that they all require you to log in to do stuff. You cannot tweet on Twitter, comment on Facebook, or email on Gmail unless you are authenticated and logged in to the service. So how does it work? How does the website authenticate us? How does it know which user is logged in and from where? Let us answer each of these questions below.
How does User Login work?
Whenever you enter your username and password on the login page of a site, the information you enter is sent to the server. The server then validates your password against the password on the server. If it doesn’t match, you get an error of an incorrect password. But if it matches, you get logged in.
What happens when I get logged in?
When you get logged in, the web server initiates a session and sets a cookie variable in your browser. The cookie variable then acts as a reference to the session created. Confused? Let us simplify this.
How does Session work?
When the username and password are right, the server initiates a session. Sessions have a really complicated definition so I like to call them ‘beginning of a relationship’.
When the credentials are right, the server begins a relationship with you. Since the server cannot see like us humans, it sets a cookie in our browsers to identify our unique relationship from all the other relationships that other people have with the server.
What is a Cookie?
A cookie is a small amount of data that the websites can store in your browser. You must have seen them here.
So when you log in and the server has created a relationship or session with you, it takes the session id which is the unique identifier of that session and stores it in your browser in form of cookies.
What’s the Point?
The reason all of this is needed is to verify that it’s you so that when you comment or tweet, the server knows who did that tweet or who did that comment.
As soon as you’re logged in, a cookie is set which contains the session id. Now, this session id is granted to the person who enters the correct username and password combination.
So the session id is granted to the person who owns that account. Now whenever an activity is performed on that website, the server knows who it was by their session id.
Keep me logged in?
The sessions have a time limit. Unlike the real world where relationships can last even without seeing the person for longer periods of time, sessions have a time limit. You have to keep telling the server that you are online by performing some of the other actions. If that doesn’t happen the server will close the session and you will be logged out.
But when we use the Keep me logged in a feature on some websites, we allow them to store another unique variable in the form of cookies in our browsers. This unique variable is used to automatically log us in by checking it against the one on the server. When someone steals this unique identifier it is called cookie stealing. They then get access to your account.
We discussed how Login Systems work and how we are authenticated on a website. We also learned about what sessions and cookies are and how they are implemented in a login mechanism. I hope you guys have grasped that how User-Login works, and if you still have a doubt regarding anything, just drop in a comment and I’ll be there for you.