Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authentication with an existing database with existing hashed (md5) passwords #398

swina opened this Issue Jan 17, 2017 · 4 comments


None yet
4 participants
Copy link

swina commented Jan 17, 2017

I am using a feathers client and server app.
Clients need to authenticate to an existing db (mysql) with passwords hashed (md5)
Using local authentication (email+password) and trying with the auth/local endpoints (with a corrected sequelize user model) I can't get authenticated.
If I try to run the users endpoint (with no authentication required) I get user data correctly.
I suppose that this is due to different password hash algorithm that fails the authentication on db.
Any help is appreciated.


This comment has been minimized.

Copy link

MidnightP commented Jan 17, 2017

I sort of have the same issue. Would be interesting to learn what kind of hashing feathers uses and if there are some options for it.


This comment has been minimized.

Copy link

guyspr commented Jan 18, 2017

You should create a custom verifier for local, see here:

To answer @MidnightP: feathers uses bcrypt by default, which you would know if you took some time to read the readme.


This comment has been minimized.

Copy link

swina commented Jan 18, 2017

Thank you, I know that feathers uses bcrypts, I was just looking for if someone else has previuosly worked on it and how has been solved. I will look inside in order to develop a custom verifier.


This comment has been minimized.

Copy link

ekryski commented Jan 20, 2017

@swina see my answer here: #289 (comment)

That should do it. I'm working on expanding the documentation to show this. Going to close this issue but feel free to comment if you have trouble.

@ekryski ekryski closed this Jan 20, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.