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 Aug 29, 2018. It is now read-only.
Whenever I try to authenticate through REST or socket, the create method on the user service gets called each time.
That means the request body gets changed and the bcrypt compare method will actually try to validate the entered password which has been just hashed due to the create method getting called on the user service against the actual database password.
None of the built-in authentication tools call create on the users service. It has to be somewhere in your code but I don't think the snippets show your entire setup. As I mentioned before, the best way to get help with things like this is to share a complete repository that can be cloned and reproduces the issue.
Whenever I try to authenticate through REST or socket, the create method on the user service gets called each time.
That means the request body gets changed and the bcrypt compare method will actually try to validate the entered password which has been just hashed due to the create method getting called on the user service against the actual database password.
How come this happens?
Config:
User service:
Authentication service:
The text was updated successfully, but these errors were encountered: