<p style="background:#fefeb4;border:1px solid #dddddd;font-weight:bold;padding:0.5em 1em;">The solution detailed in this guide is fairly complex and may not be ideal for most users.<br />
We recommend you check out the solutions detailed in [[Managing multiple clients and their repositories]] first.</p>
<h2>The Problem</h2>
<p>One might encounter a situation where two GitHub accounts might be necessary. Naturally, I mean two <strong>pay</strong> accounts in order to remain in good standing according to the <span class="caps">TOS</span> (or one free and one pay account). And we all want to stay in good standing with GitHub since they were awesome enough to make this great web application, right? Nevertheless, with that said, one might find one’s self in this situation.</p>
<p>A problem that one is likely to encounter in this situation is attempting to maintain two or more repositories that use more than one GitHub account. Using the default public/private key setup that GitHub suggests works great when only one account is involved, but when one attempts to clone a repository using a second account, by default, git attempts to use the first account, which is likely declined resulting in failure.</p>
<p>This article is assuming that you already have two git accounts created and that you already have the first <a href="http://github.com/guides/providing-your-ssh-key">key pair</a> in place on both your local system and on GitHub.</p>
<h2>Generating a Second Key Pair</h2>
<p>Read this section <span class="caps">COMPLETELY</span> before actually doing anything. You could easily get yourself into a lot of trouble if you do not. GitHub identifies which account you are attempting to access by the <span class="caps">SSH</span> key that you give it. To this end, you cannot use the same key pair for more than one GitHub account. You will need to follow the instructions given in the guide entitled <a href="http://github.com/guides/providing-your-ssh-key">Providing your <span class="caps">SSH</span> Key</a>. I think it would be unwise to reproduce part of that guide here.</p>
<p>Upon executing the ssh-keygen command, you will be presented with a prompt similar to the following:</p>
<pre class="console">Enter file in which to save the key (/Users/tom/.ssh/id_rsa):</pre>
<p><b><span class="caps">WARNING</span></b>: If you already had a key pair and are using it for anything at all, do <span class="caps">NOT</span> leave this blank nor should you use the default file suggested. It will overwrite your primary key pair, and that would be very bad.</p>
<p>Instead of using “id_rsa”, you should use something like “id_rsa_github_useraccount” to denote the purpose of the key. So ultimately, you would enter:</p>
<pre class="console">/Users/tom/.ssh/id_rsa_github_useraccount</pre>
<h2>Placing the Public and Private Keys</h2>
<h3>Private Key</h3>
<p>You will not actually be putting the private key anywhere, but instead only referencing it. For this, you will need to open the <span class="caps">SSH</span> config (~/.ssh/config) file in your favorite editor. Once in this file, you should add the following:</p>
<pre><code># GitHub for cylence
Host github-tom
HostName github.com
User git
IdentityFile /Users/tom/.ssh/id_rsa_git_tom</code></pre>
<p>The top line is a simple comment, you can leave this out of you choose. Next is the name of the Host, this is what you will use when referencing this connection and after the word “Host” followed by a space is completely arbitrary. The HostName must be “github.com” as is the same with the User.Notice that it is still “git” and not an account name. Lastly, the IdentityFile line must contain a non-reative path to your newly created private key (<span class="caps">NOT</span> ending with .pub).</p>
<h3>Public Key</h3>
<p>Once the private key is properly being referenced, you must tell GitHub what the public key is. You do this by accessing your <a href="http://github.com/account">account page</a> on GitHub. Place your public key (including the carriage return at the end) into the “<span class="caps">SSH</span> Public Keys” textarea field.</p>
<h2>Using the Newly Created Keys</h2>
<p>From here on, everything is the same except for one component. To present an example, we will look at a standard clone command.</p>
<pre class="console">git clone git@github.com:account/repository.git</pre>
<p>Traditionally, this command consists of “git clone”, the command to be performed, followed by a mostly ordinary ssh connection.</p>
<pre>user@domain:path/somewhere/file.extension</pre>
<p>What we will be changing is the domain portion of this line. Instead of using the domain “github.com”, we will be specifying the pre-configured <span class="caps">SSH</span> connection we built earlier. It is referenced using the Host line. Using our previous example, the end result would look like this:</p>
<pre class="console">git clone git@github-tom:account/repository.git</pre>
<h2>Notes</h2>
<p>If you are running keychain to manage your <span class="caps">SSH</span> keys you may need to stop ssh-agent and add the new key to your keyring for it to work properly. If you are seeing failed access to your repositories as your other user, even though you’re configured to use the new key with your correct user you may wish to give this a try. On <span class="caps">OSX</span> Leopard is built in keychain integration, so either don’t store your passphrase in keychain or don’t use passphrase for your private key at all.</p>
<p>Regarding multiple local keys and ssh-agent, be sure to add each key with ssh-add, you can also try prefixing your git commands (when interacting with the remote repo) with SSH_AUTH_SOCK="", which will make ssh not use the ssh-agent.</p>
2008-04-24T16:24:28-07:00
42
multiple-github-accounts
Multiple GitHub Accounts
2009-10-19T05:13:40-07:00
140313