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

Password change #56

Closed
whoisstan opened this issue Feb 21, 2013 · 12 comments
Closed

Password change #56

whoisstan opened this issue Feb 21, 2013 · 12 comments

Comments

@whoisstan
Copy link

I had to change my heroku password and have had trouble ever since authenticating with heroku using the command line. I found out that actually removing the heroku accounts plugin does the trick.

http://stackoverflow.com/questions/10628149/unable-to-use-heroku-gem-cli-after-password-changes

However if I add it back again I am having the same issue. Is there a way to refresh the authentication information?

@mikecarroll
Copy link

I'm having this issue, too. Get prompted for password, enter correct password, still get an "Authentication failed" error.

@neilvcarvalho
Copy link

Another one having this issue here. Removing the account and readding it worked, though. I didn't have to remove the whole plugin.

@i8ramin
Copy link

i8ramin commented Dec 18, 2013

+1 ... same issue. Had to remove the plugin to login via CLI. Adding the plugin again doesn't work for me. Will try removing the account and re-adding it.

@Technicolor
Copy link

+1 Same issue occurred for me as well.

@memoht
Copy link

memoht commented Apr 9, 2014

+1 on this issue. I just updated my Heroku password due to the Heartbleed Open SSL bug. I was not able to login from CLI until I used heroku accounts:remove then re-added by using heroku accounts:add. This gotcha is going to get some people. Still, this plugin has been very useful for managing multiple accounts. Hope this issue gets addressed.

@mokolabs
Copy link

Yeah, I also ran into this same issue after I updated my Heroku account passwords for #heartbleed. ❤️

If you delete the heroku-accounts plugin before removing your pre-existing accounts, you may put your setup into a bad state, as i did.

I'm kept getting an error that one of my heroku accounts could not be found... and there was no way to fix it after I removed the plugin. I even tried installing the plugin again, but I got the same error. My hunch is the heroku app I was working on kept trying to load the saved account info, but it no longer existed.

Here's what I did to resolve it:

  • Uninstalled the heroku-accounts plugin
  • Ran rm -rfd ~/.heroku/accounts to delete my existing cached accounts
  • Reinstalled the heroku-accounts plugin
  • Added each of my accounts using heroku accounts:add [account nickname]

You also might want to double check your ~/.ssh/config file to confirm that you are using the same account nicknames as before to prevent other potential problems.

We should probably update the README docs to make it explicitly clear that you must update account passwords by deleting and then re-adding accounts.

@jaredbeck
Copy link

I also ran into this same issue after I updated my Heroku account passwords for #heartbleed.

Same here. Uninstalling heroku-accounts fixes the problem.

heroku plugins:uninstall heroku-accounts
rm -r ~/.heroku/accounts
heroku logout
heroku login

@nathany
Copy link

nathany commented Apr 14, 2014

Just ran into this too. Probably a lot of people will due to Heartbleed password resets.

I see that ~/.heroku/accounts contains a password hash.

@nathany
Copy link

nathany commented Apr 14, 2014

@mokolabs I ran into the heroku "account not found" loop too. From #26 git config --get heroku.account and remove it with git config --unset heroku.account

@mokolabs
Copy link

@nathany Awesome. Thanks!

@costa
Copy link

costa commented Apr 22, 2014

So, what worked for me was:

  • heroku accounts:remove ACCOUNT
  • heroku accounts:add ACCOUNT # enter credentials, no need to re-generate the keys AFAIK
  • git config --add heroku.account ACCOUNT # for each project

I've seen no need to git config --unset heroku.account but I might have missed something.

@ddollar
Copy link
Owner

ddollar commented Nov 7, 2014

Hello. I apologize for the delayed response. I am currently declaring issue bankruptcy. If this issue still applies to you please feel free to re-open and explain. Thanks :)

@ddollar ddollar closed this as completed Nov 7, 2014
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