Skip to content
This repository has been archived by the owner on Feb 22, 2021. It is now read-only.

can't create an account/ sign in. Password entry bug #118

Closed
vrnico opened this issue Mar 10, 2018 · 5 comments
Closed

can't create an account/ sign in. Password entry bug #118

vrnico opened this issue Mar 10, 2018 · 5 comments

Comments

@vrnico
Copy link

vrnico commented Mar 10, 2018

passwordissue

I've tried making/ signing in with a Google account on a self-hosted herokuapp, and on the usevolition.com portal. While I can't get the self-hosted sign up or sign on to work, I have been able to access my account through signing in through my Google account on the usevolition portal. Upon trying to sign up for an account on volition.com and in my heroku app I am unable to complete the form post because it is failing to reference it against the 100 most common passwords (pictured above). Any ideas on how to fix this?

Also any guidelines on running volition without authentication on a local vm?

@harshamurthy
Copy link
Collaborator

@vrnico, I'm looking into it. I'll try to recreate the issue on my end and figure out the solution. Will get back to you asap!

@harshamurthy
Copy link
Collaborator

@vrnico, thanks for your patience! I looked into what you said above:

  1. Google account sign-in is disabled on self-hosted versions of Volition. Creating an account and signing in to the version of Volition we host at https://www.usevolition.com will create an account completely separate from your self-hosted account. You should not even see the option to sign in with Google on your self-hosted version.
  2. The top 100 passwords check we were using was taken down which is what was causing the error when you were trying to create an account on your self-hosted version. I have submitted a pull request fixing this issue. It should be reviewed and merged into the master branch by tomorrow morning. Thanks for bringing that error to our attention!
  3. Running Volition without authentication is a bit more complicated than it would seem. All of the information from to-dos and weekly plans are associated with a specific user, which requires authentication even if yours is the only account in the database because you are self-hosting.

I'll let you know as soon as the password error resolution is merged into the master branch. You can then redeploy to Heroku and sign up on your self-hosted version successfully!

@harshamurthy
Copy link
Collaborator

@vrnico, the fix has been pushed to master. Feel free to redeploy, you should be able to create an account on your self-hosted version without any issues now.

@vrnico
Copy link
Author

vrnico commented Mar 17, 2018

@harshamurthy hey just redeployed, and was able to sign in! solid job!

@marcopatr
Copy link

Could it be that the error exists again? On a self-hosted herokuapp I see the same as the screenshot shows above. A login is not possible.

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

No branches or pull requests

3 participants