Files
noisedash/server/boot/auth.js
Kevin Thomas 9571cd0224 Debug sessions
2021-07-26 16:17:51 -07:00

55 lines
2.0 KiB
JavaScript

const passport = require('passport')
const Strategy = require('passport-local')
const crypto = require('crypto')
const db = require('../db')
module.exports = function () {
// Configure the local strategy for use by Passport.
//
// The local strategy requires a `verify` function which receives the credentials
// (`username` and `password`) submitted by the user. The function must verify
// that the password is correct and then invoke `cb` with a user object, which
// will be set at `req.user` in route handlers after authentication.
passport.use(new Strategy(function (username, password, cb) {
db.get('SELECT rowid AS id, * FROM users WHERE username = ?', [username], function (err, row) {
if (err) { return cb(err) }
if (!row) { return cb(null, false, { message: 'Incorrect username or password.' }) }
crypto.pbkdf2(password, row.salt, 10000, 32, 'sha256', function (err, hashedPassword) {
if (err) { return cb(err) }
if (!crypto.timingSafeEqual(row.hashed_password, hashedPassword)) {
return cb(null, false, { message: 'Incorrect username or password.' })
}
const user = {
id: row.id.toString(),
username: row.username,
displayName: row.name
}
return cb(null, user)
})
})
}))
// Configure Passport authenticated session persistence.
//
// In order to restore authentication state across HTTP requests, Passport needs
// to serialize users into and deserialize users out of the session. The
// typical implementation of this is as simple as supplying the user ID when
// serializing, and querying the user record by ID from the database when
// deserializing.
passport.serializeUser(function (user, cb) {
console.log('serializing user: ');
process.nextTick(function () {
cb(null, { id: user.id, username: user.username })
})
})
passport.deserializeUser(function (user, cb) {
console.log("DESERIALIZE")
process.nextTick(function () {
return cb(null, user)
})
})
}