See all blog posts ↑

OpenID with Google and GitHub

Vincent Viallet on

I doubt I need to explain what OpenID, the decentralized authentication standard, is. You may actually use it without knowing it as quite a few companies are indeed OpenID providers. We find it especially handy for providing admin credentials to our staff when we build products, and doing so without having to specify user passwords in clear in our code base.

We had been using MyOpenID for a while; it allowed us to manage accounts for our staff in a centralized fashion. Unfortunately, the service proved to be unreliable and we could not get support from its owners. None of the other providers seemed to allow us to manage multiple accounts for our domain name, so we settled for setting up our own OpenID service. We are pretty averse to maintaining services on our own; we happily delegate to Github, Dropbox, Linode, HelloFax and the likes. Our solution had to be easy to maintain, and if possible running on servers we’re not responsible for.

The approach we took, and that I will describe below, leverages Google as the OpenID provider and Github to redirect our company URLs.

Enabling OpenID on your Google account

Whether you have a personal or professional GMail account, you should be able to activate OpenID for your Google account. It is fairly straightforward, however you will be required to enable Google+ to do so:

  1. Enable Google+ for your email account,
  2. In your web mail interface, click on privacy on the top right, OpenID screenshot
  3. Get the long number in the following format:\_VERY\_LONG\_NUMBER - the very long number is your profile ID,

However, the OpenID provided by Google is not really convenient; I happen to address my colleagues with their surname, rarely with their Google+ serial number. Google’s alias ain’t exactly what we call unique and not really suitable as an OpenID URL on any website. That’s when Github comes in handy, allowing us to alias URLs like\_VERY\_LONG\_NUMBER into

Set up Github

We already host quite a few sites on GitHub, leveraging the awesome Github pages feature. We here just want to redirect our custom URLs to the appropriate Google+ accounts;

  1. Create a new github repository (public or not, as long as you’re fine with exposing your list of users),
  2. Create a new branch gh-pages and switch to it,
  3. Create a file called CNAME, simply put the domain name you want to use to access the site (in our case:
  4. For each user, you will need to create a file to handle the redirection to his Google+ account, for example bob.html with the following content;

        <link rel="openid2.provider" href="">
        <link rel="openid2.local_id" href="">
  5. Commit and push to Github,
  6. Update your DNS with an entry pointing the domain name you defined in the “CNAME” file to Github.

You can now use your OpenID with your own domain name; in the previous example it would be something like You obviously need to be logged in your Google account for things to work.

You can have a look at our company repository if you’re wondering how this might look like.