-
Notifications
You must be signed in to change notification settings - Fork 118
Server crashes when authenticating with Socket.io transport and no user entity service exists #526
Comments
It appears this can be fixed by checking to see if |
I think I have a similar problem issue
It looks like the entity is not configured in strategyOptions, this is my configuration file, where is it wrong? Or did I find a bug? "authentication": {
"secret": "....",
"strategies": [
"jwt",
"users",
"operators"
],
"path": "/authentication",
"jwt": {
"header": {
"typ": "access"
},
"audience": "https://yourdomain.com",
"subject": "anonymous",
"issuer": "feathers",
"algorithm": "HS256",
"expiresIn": "1d"
},
"entity": "user",
"service": "users",
"users": {
"entity": "user",
"service": "users",
"usernameField": "phone",
"passwordField": "device",
"session": false
},
"operators": {
"entity": "operator",
"service": "operators",
"usernameField": "email",
"passwordField": "password",
"session": false
}
} Through http everything works perfectly, this only happens with sockets. |
i was also facing that issue and i have solved by applying this code i got solution. |
Feathers v4 authentication supports not using an entity service at all. Please see the migration guide for more information. Closing this issue in order to archive this repository. Related issues can be opened at the new code location in the Feathers main repository. |
Steps to reproduce
authentication.service
andauthentication.path
blank in the config filejwt
strategyExpected behavior
A connection should be established and authenticated
Actual behavior
The server crashes with the following error:
System configuration
Module versions:
NodeJS version: v7.9.0
Operating System: Mac OS X
Browser Version: Chrome v58.0.3029.110 (64-bit)
Module Loader: Webpack v2.2.1
The text was updated successfully, but these errors were encountered: