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 has been archived by the owner on Mar 22, 2022. It is now read-only.
…to authentication hooks
Makes those parameters specified in `socket.feathers.data` or `req.feathers.data`, when setting up SocketIO and Primus respectively, available to the authentication hooks as they would be elsewhere in a Feathers application.
…oks (#477)
Makes those parameters specified in `socket.feathers.data` or `req.feathers.data`, when setting up SocketIO and Primus respectively, available to the authentication hooks as they would be elsewhere in a Feathers application.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In my application I need to pass certain information about the connection/request to hooks on some of my services, including my
users
service.https://github.com/feathersjs/feathers-authentication/blob/master/src/socket/handler.js#L58 forbids this by not including the
socket.feathers
object (if available), thus the only data available to the authentication hooks over socket/primus is that specified on the aforementioned line 58.Given:
The result of an authentication attempt always results in:
where the ideal situation would result in:
I have cobbled together a quick fix for my application for the time being. I will clean it up, instrument/test it, and submit a PR to resolve.
The text was updated successfully, but these errors were encountered: