auth: draft jwt support using gapitoken

[proppy]

Fixes #5, modeled after the compute client.

[proppy]

Note that the current implementation require you to confert the p12 file into PEM using:

openssl pkcs12 -in key.p12 -out key.pem -nocerts

And always ask for a passphrase:

Enter PEM pass phrase:

There seems to be PKCS12 support in node.crypto so there might be a workaround for the converstion.

One could get rid of the passphrase using:

openssl rsa -in key.pem -out key-nopass.pem

[rakyll]

Your base is not google:master, fetch and merge.

[proppy]

It's from a fresh clone:

~/google-api-nodejs-client$ git pull origin master
git pull origin master
From https://github.com/google/google-api-nodejs-client
 * branch            master     -> FETCH_HEAD
Already up-to-date.
~/google-api-nodejs-client$ git push proppy jwt
git push proppy jwt
Everything up-to-date

[rakyll]

My bad, broken tests...
I'm not quite sure about the current naming, two concerns.

• Currently, we call all auth middleware xxxAuthClient but it's quite verbose, so I don't want to keep naming auth clients in a similar fashion.
• JWT doesn't represent the OAuth 2.0's client authorization, as Google calls it, service account based authorization.

[proppy]

Currently, we call all auth middleware xxxAuthClient but it's quite verbose, so I don't want to keep naming auth clients in a similar fashion.

Can we do this in a separate, refactoring change? I created #77 to track it.

JWT doesn't represent the OAuth 2.0's client authorization, as Google calls it, service account based authorization.

Do you want me to rename it to serviceaccount? I wanted to make the distinction between JWT based service account, and platform specific ones like compute or app engine.

[rakyll]

To be accurate, it should be as verbose as oauth2serviceaccount.

[proppy]

It is called jwt in Go :)
https://code.google.com/p/goauth2/source/browse/oauth/jwt/jwt.go

[proppy]

PTAL

[proppy]

tests fixed: PTAL