Access to User db object about mongoose-auth

More info - my req.session after a successful facebook authentication looks like this:

{
  "lastAccess":1303841289370,
  "cookie":{
    "originalMaxAge":14400000,
    "expires":"2011-04-26T22:07:38.878Z",
    "httpOnly":true,
    "path":"/"
  },
  "auth":{
    "facebook":{
      "user":{
        "id":"610771581",
        "name":"Jason Bond Pratt",
        "first_name":"Jason",
        "middle_name":"Bond",
        "last_name":"Pratt",
        "link":"http://www.facebook.com/jasonbondpratt",
        "username":"jasonbondpratt",
        "hometown":{
          "id":"107442005952063",
          "name":"Hartford, Michigan"
        },
        "location":{
          "id":"110184922344060",
          "name":"Washington, District of Columbia"
        },
        "gender":"male",
        "email":"[email protected]",
        "timezone":-4,
        "locale":"en_US",
        "verified":true,
        "updated_time":"2011-04-16T22:09:12+0000"
      },
      "accessToken":"XXXXXXXXXXXXXXXXXXXXX"
    },
    "loggedIn":true
  }
}

[bnoguchi]

Rolling out a req.user accessor within the hour. Stay tuned.

[bnoguchi]

npm install the latest v0.0.6

From your express server code, you now will have access to req.user

From your express views, you now will have access to both

• everyauth.user
• user

which equivalently return the mongoose User document associated with the current session

AWESOME.

This is great - originally I had some problems, as I missed the update in everyauth that requires the findUserById function to be defined, works great now. That being said - maybe mongoose-auth could provide that definition by default, since it has access to the User model (via it's configurable User function) and knows that it's using Mongoose. Anyway just an idea.

[bnoguchi]

mongoose-auth does provide a default findUserById definition. If you check the README, you do not have to define findUserById for mongoose-auth, since it does it for you automatically.