Home/ Questions/Q 6619343
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T20:57:17+00:00

I want to have an auto login option check for a user. Basically that

  • 0

I want to have an auto login option check for a user. Basically that means a cookie will be stored on the client side.

Now the question is, how do I make it secure so the cookie will can not be spoofed/modified.

One of my friends suggest having a db table that stores the session_id, user’s ip, browser info, etc and then compare it all that information once a user goes to the website again.

I feel like having a separate table for that is a bit too much trouble. Is there another way to do it? Maybe with tokens or something like that?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The more secure you want this infamous cookie, the more trouble it’s going to be for you. If your users should be particularly secure, you will have to go with the most troublesome approach.

    You should only accept this cookie with https if you want to be as secure as possible. If the cookie is accepted over http, it can be sniffed and stolen.

    I would recommend that the cookie have no user data at all (a token, as you suggested). This will, unfortunately, require another table. When a user logs in and chooses “keep login,” create an entry in this table. The entry can be any meaningless value (such as md5(uniqid('', true));. This token can be unique in the DB and mapped to a user’s ID.

    When a user visits your website, you can check the value of that cookie and get the user it belongs to and log them in. At this point, you destroy the old token and create a new one. “Destroy” can mean many things. You can delete it from the DB entirely or have a flag that disables the token. You may want to allow the same token to be used multiple times in case the cookie is received but the authentication doesn’t go through for some reason, but I think this is insecure. You may also want to store the timestamp of the token and only accept it if it’s been some limited period of time (30 days for example).

    As your friend points out, you can store other information such as user agent, IP address, etc., but these may change even with the same browser being used (especially with mobile) and if a user’s persistent login is not accepted because of this, it could be jarring and inconvenient to them.

    If you really don’t want to create another table, then you will have to store some way to acquire the user’s ID from the cookie value. This is less secure.

    • 0