You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 22, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 22, 2022. It is now read-only.
I think you could implement the lastLoggedIn on two services. (Related to the third question, you can use hooks on auth services.) I'd put one on the auth/local service as an after hook, and another on the users service, which would probably make the most sense as a before hook for when new login details are being saved to the user during an OAuth login.
Activity
marshallswain commentedon May 24, 2016
@justingreenberg Sounds great! We would love the help.
I think you could implement the
lastLoggedInon two services. (Related to the third question, you can use hooks on auth services.) I'd put one on theauth/localservice as an after hook, and another on theusersservice, which would probably make the most sense as a before hook for when new login details are being saved to the user during an OAuth login.For socket presence, both socket.io and Primus keep a list of connected users, which is used here: https://github.com/feathersjs/feathers-socket-commons/blob/e357f8d7d98f5ec11d9c687d1cba51899079852f/src/events.js#L79
and passed from here: https://github.com/feathersjs/feathers-socket-commons/blob/e357f8d7d98f5ec11d9c687d1cba51899079852f/src/index.js#L15. I'm not sure if it will contain the user information you need, but that's the first place I'd check.