{"id":1026,"date":"2017-01-01T22:31:19","date_gmt":"2017-01-02T06:31:19","guid":{"rendered":"http:\/\/breanneboland.com\/blog\/?p=1026"},"modified":"2017-01-01T22:39:33","modified_gmt":"2017-01-02T06:39:33","slug":"restoring-github-repo-access-in-terminal-after-adding-2fa","status":"publish","type":"post","link":"https:\/\/breanneboland.com\/blog\/2017\/01\/01\/restoring-github-repo-access-in-terminal-after-adding-2fa\/","title":{"rendered":"Restoring Github Repo Access in the Terminal after Adding 2FA"},"content":{"rendered":"

\"Molding,<\/p>\n

This is the second time I’ve had to look this up, and the instructions are spread across a couple of pages. So for the sake of my future self, I’m compiling the steps here. Maybe it’ll help someone else too. That’d be cool.<\/p>\n

So you added 2FA to your Github account. (Very smart; nice job.) Problem: your terminal no longer accepts your (still valid) password when you’re trying to push to a repo. Here’s how to fix that.*<\/p>\n

1. Create a new personal access token.<\/h2>\n

Go to Github and ensure you’re logged in. (An aside: you’ve saved your access codes in a password manager or some other secure place in case the device you designated for 2FA authentication codes catches on fire, right? Excellent, carry on.)<\/p>\n

Go to the upper-right corner of the page, click your profile image, and click\u00a0Settings<\/strong>. In the sidebar of the next page, scroll to the bottom and click\u00a0Personal access tokens<\/strong>. Click\u00a0Generate new token<\/strong>. Give it a name that will make your future self grateful for today’s clarity. Select what permissions you want this token to give. Then:\u00a0Generate token<\/strong>. The token that appears will only be visible right now, so make sure you save it or do what you need to do with it. (Or save it to 1Password and then proceed to the next step.)<\/p>\n

2. Save it to your OSX keychain credentials<\/h2>\n

Here’s the choose your own adventure part: do you have Github credentials saved for more than one Github account on this machine?<\/p>\n

2a. Nah, just one. Let’s nuke it and replace it.<\/h3>\n

Cool, let’s get rid of the old credential first. Go into your terminal and type this:<\/p>\n

git credential-osxkeychain erase<\/span><\/pre>\n
There’ll be a pause and then nothing. That means success. (I still find this convention strange, but I like a verbose interface, so that’s my own struggle to deal with.)<\/p>\n
Now, do that push that you were probably trying to do when you realized you’d cut off access on a machine you perhaps\u00a0don’t code from so often. It’ll ask you for your username and password. Give it your username as usual, but instead of your password, paste that\u00a0Personal access token\u00a0<\/strong>that we created in the last step into the terminal. Hit enter. Wait. Enjoy your success (which will be confirmed by a message this time).<\/p>\n
2b. I’m super cool and access SO MANY accounts. Let’s just replace one, please.<\/h3>\n
Alright, fancy. For this one, we’ll start with the\u00a0Keychain Access\u00a0<\/strong>app instead of the terminal. (Don’t worry, we’ll finish in the terminal for this step too, if you prefer.) Open Keychain Access and then type in “Github” to narrow down the options listed. You’re looking for an entry for github.com. To confirm you’re looking at the right one, ^click and select “Get info” from the menu that appears. Confirm that the username you’re looking for is the one listed under account<\/em>, then select Access Control and confirm that the option listed is git-credential-osxkeychain. If those two things look right, we’ve found the right credential.<\/p>\n
Now you can edit it there, replacing the existing password with your new token, or you can delete it and provide the new credential via the terminal when prompted after you try to push again, as described in 2a.<\/p>\n
There you go! Such security, what authentication.<\/p>\n
Want to double-check my work? Here’s what I used to put together these steps (both times, because sometimes that’s what it takes):<\/p>\n