re: Best way to store password in DB VIEW POST

FULL DISCUSSION
 
  1. use TLS and HSTS so that your connection will be encrypted. It doesn't make it impossible but it makes it a lot harder. You can also use non-SMS based 2FA to increase security.

  2. why aren't you allowed to store hashed passwords or use authentication libraries? You should never store passwords in clear. BTW don't use SHA256 if you can avoid it, there are better algorithms like Argon2 or the older PBKDF2

 

Have an assignment to build account-password system without npm auth package.Whats the best approach

 

Kambala - depending on the definition of "db", could you consider vaultproject.io/? It's possible a little OTT for (what sounds like) a student assignment, but it's built to store passwords securely.

 

I'm not a node user so I'm going to be generic. Let's start with a "shopping list" of what you might need:

  • a database to store the accounts
  • a library to connect to such database
  • a user table in the database, the minimum is probably "username", "password"
  • a library to hash those password
  • a web framework and HTML/CSS to render the registration and login pages

The registration flow is:

  • input username, password and password confirmation
  • check the two passwords, if they are equal hash one and store it in the db with the username, if they are not equal tell the user
  • redirect the user to a "success" page

The login flow is:

  • input username and password
  • hash the password and check it's the same one you have stored
  • if it is, let the user in, if not, tell them
  • redirect the user to a "success" page

This is the bare, bare, minimum.

Keep in mind that since there are no sessions in this scenario, the user will have to input their accounts everytime they decide to access the "protected" page.

 

Probably not directly helpful for what looks like a learning exercise in "things you shouldn't do unless you have to", but in the real world I would always look to delegate this part of an application to something sane like auth0.com, or AzureAD, or Facebook, Google, Twitter... much like your favourite dev website :)

More useful - all the stuff @rhymes said!

code of conduct - report abuse