It would be better to use bcrypt, beause its more secure as it's slower (uses more computing cycles).
Your code could also be better:

You wouldn't need salt field in User model, because it's saved into the same field as password does.

For authentication, something like:

var mongoose = require('mongoose'),
  bcrypt = require('bcryptjs');

var userSchema = mongoose.Schema({
  email: String,

Acceptance criteria

• Name: Break the word and show the name in the second line.
• Email: Truncate the email address, show full email address on hover.
  Provide a button on the right to copy the full email addre

Currently our preflight/ endpoint is accessible at any time, even after the instance has already been correctly deployed. We should remove these routes after the app has been deployed (i.e. at least one user has been created in the instance), to avoid potentially leaking some information about the instance's setup (as we add more functionality to this page). To accomplish this,

• The `_prefligh

Problem
Users can set custom metadata on their customers, but we currently don't display this information anywhere in the UI.

This is what we currently display:

Solution
Using this metadata field on the customer o

Context

• This is part of release-1.5 #148
• MEDIUM priority task

Tasks

• Remove dependency bcrypt-nodejs in package.json
• Add dependency bcrypt in package.json
• Migrate file app/data/user-dao.js to bcrypt
• Validate the instalation with the local test
• Add and submit the chang