Fix for linked account information bug

Somtimes linked accounts were being displayed incorrectly.

The seralisation code has been updated to fix this with both Mongo DB and NeDB (used when no Mongo DB is configured).

NextAuth also has an update to it’s error handling to reduce future errors so have updated the dependancy.

Author: iaincollins

next-auth.functions.js

@@ -122,7 +122,14 @@ module.exports = () => {
       },
       // Seralize turns the value of the ID key from a User object
       serialize: (user) => {
-        return Promise.resolve(user._id)
+        // Supports serialization from Mongo Object *and* deserialize() object
+        if (user.id) {
+          return Promise.resolve(user.id) 
+        } else if (user._id) {
+          return Promise.resolve(user._id) 
+        } else {
+          return Promise.reject(new Error("Unable to serialise user"))
+        }
       },
       // Deseralize turns a User ID into a normalized User object that is
       // exported to clients. It should not return private/sensitive fields.

npm-shrinkwrap.json

@@ -22,7 +22,7 @@
     "mongodb": "^2.2.31",
     "nedb": "^1.8.0",
     "next": "^4.2.1",
-    "next-auth": "^1.1.1",
+    "next-auth": "^1.1.5",
     "next-auth-client": "^1.1.1",
     "node-sass": "^4.5.3",
     "nodemailer": "^4.0.1",