New login screen fails with useEncryptedPasswords

[Muesly]

I've upgraded to 1.0.21 and the new login screen, which appears fine, but come up with this page when entering in my details:

Error: Illegal arguments: undefined, string
at Error (native)
at Object.bcrypt.compareSync (/Users/tony/Code/Lost/parse-dashboard/node_modules/bcryptjs/dist/bcrypt.js:230:19)
at /Users/tony/Code/Lost/parse-dashboard/node_modules/parse-dashboard/Parse-Dashboard/Authentication.js:91:65
at Array.find (native)
at Authentication.authenticate (/Users/tony/Code/Lost/parse-dashboard/node_modules/parse-dashboard/Parse-Dashboard/Authentication.js:88:21)
at /Users/tony/Code/Lost/parse-dashboard/node_modules/parse-dashboard/Parse-Dashboard/Authentication.js:40:21
at pass (/Users/tony/Code/Lost/parse-dashboard/node_modules/passport/lib/authenticator.js:347:9)
at Authenticator.deserializeUser (/Users/tony/Code/Lost/parse-dashboard/node_modules/passport/lib/authenticator.js:352:5)
at SessionStrategy.authenticate (/Users/tony/Code/Lost/parse-dashboard/node_modules/passport/lib/strategies/session.js:53:28)
at attempt (/Users/tony/Code/Lost/parse-dashboard/node_modules/passport/lib/middleware/authenticate.js:348:16)

I have the setting "useEncryptedPasswords" : true in my config, and login worked in 1.0.19 with the same config.

Any ideas?

[sidan5]

Same here!

[jpm]

Same here. Setting the parse-dashboard package version to 1.0.19 fixes the problem.

[drizzt]

Nice unit tests ;)

[richard4339]

So Ubuntu only supports node 4.2.6, and parse-dashboard requires 4.3. I initially assumed it was related to this, but upgraded to the latest version and it still fails.

[bdevore17]

Having same issue. Getting "Internal Server Error"

[dvanwinkle]

I'll look into this tomorrow morning. I wrote the original encrypted passwords part, but, haven't upgraded to the latest version with the login screen yet.

Thanks for reporting this @Muesly!

[dvanwinkle]

Ah, looks like @lsohn already fixed this in #609. It has been accepted and merged into master already.

This can be closed @flovilmart.

[richard4339]

Will there be a new release soon since this seems like a pretty major bug?

Edit: I manually applied the patch from #609 and I can confirm for those waiting on a release it does fix the problem

[jankcat]

Any ETA on this being put into a release?

[bdevore17]

Looks like @flovilmart just cut the release fixing this issue.

[flovilmart]

yes, available on NPM: https://www.npmjs.com/package/parse-dashboard
and docker: https://hub.docker.com/r/parseplatform/parse-dashboard/tags/

I appologize to the other maintainers for cutting the line of the PR flow 🙇

[hatpick]

It's still failing on 1.0.22
After I enter my credential, it says invalid username or password.
Removing useEncryptedPasswords solves the issue. Let me know if you need more information.
I had the issue since updating from 1.0.18 to 1.0.19. #588

[mldb]

same here