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

Unable to login to the demo with given credentials #59

Closed
aleixfabra opened this issue Oct 10, 2016 · 7 comments
Closed

Unable to login to the demo with given credentials #59

aleixfabra opened this issue Oct 10, 2016 · 7 comments

Comments

@aleixfabra
Copy link

Sign in with the username demo@keystonejs.com and the password demo

@tmartin2089
Copy link

Same problem. Confirmed in DB that username and password are correct.

@n-lavrenko
Copy link

+1
Also I get 500 error and response:

{
  detail: "Not a valid BCrypt hash.",
  error: "bcrypt error"
}

I think the problem is in password validation rules: the basic password is plain text: 'demo'
We need to encrypt password and replace 'demo' in /updates/0.0.1-admins.js to encrypted password.

@robhung
Copy link

robhung commented Nov 18, 2016

Works fine for me

@FLYBYME
Copy link

FLYBYME commented Nov 19, 2016

Yeah Im getting the same issue

@bjwyse
Copy link

bjwyse commented Dec 6, 2016

The protection on the User model is preventing the password from being encrypted when creating the admin user.

A workaround is to change isProtected to false for the user data in https://github.com/keystonejs/keystone-demo/blob/master/updates/0.0.1-admins.js#L13.

Then drop the database and restart. This was fine for me as I don't care about the user protection at all.

@jstockwin
Copy link
Contributor

@bjwyse Is correct above.
Authentication works fine at http://demo.keystonejs.com/, but when you clone it locally the protection is an issue.

If you're trying to get it to work locally, either edit the updates/0.0.10admin.js to remove line 13, and drop the database as suggested above, or simply add a new updates/0.0.2-user.js file, which is identical, but with different user credentials and again no line 13. That way you don't have to drop the database.

I've created an issue on the keystone side of things to see if we can address encryption not working properly when isProtected is set to true.

If people have any insight into this/want to help fix it, let's pick this up on that issue.

@nouphaltklm
Copy link

nouphaltklm commented Feb 20, 2019

Now the username & Password is user@keystonejs.com and admin. Installed via yo. Found the credentials under keystone-starter/updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants