fix withId
return hashed_pass for now, mass sets wipe othewise
allow read/write from server, so you can write REST functions
bug fix with registering provider account to existing session user
some cleanup on previous
express is a package.json requirement - how hasn't this been an issue before
remove server read/write access for now
don't create new staging user on REST calls
allow customAccessControl callback option passed into derby-auth initialization if you
want to define your own accessControl (otherwise, user.* locked down
to logged in user)
change to meet new racer#master accesscontrol using onErr as last paramter
Revert "change to meet new racer#master accesscontrol using onErr as last paramter"

This reverts commit 8c8d599c8602a823415aac68afd0f6c269e189b2.
Changed the accept functions to reflect the racer readme
Fixed Register and login
- The issue was with how the params were being setup and called
Racer params for query access will be
 | queryAccess(<collection>,<method>, function(<all params for the expose>,accept,err)
Fix for twitter auth
- Will try other auth once twitter is verified
Cleanup
Clean up
Tested twitter, facebook, and local strategies on local app
Merge pull request #19 from jasonmanners/register_fix

Updates to queryAccess and Provider Auth Login
declare specific accessControls
place passport.use() directives outside expressApp.use() directives,
I *believe* this is what was causing our memory leaks
cleanup - we don't need a separate _fetchUser funciton, and this way we can have custom err messages