Browse files

updated README instructions for the new Google Developers console

  • Loading branch information...
extrabacon committed Jan 27, 2014
1 parent 92f4e1e commit f3e91c07d6b1871bb0192e0134eb81d3188991bb
Showing with 13 additions and 19 deletions.
  1. +13 −19
@@ -40,22 +40,29 @@ You must keep the private key secure with your application so that you can sign
The application requests a token that can be used for authentication in exchange with a valid JWT. The resulting token
can then be used for multiple API calls, until it expires and a new token must be obtained by submitting another JWT.
-### Creating a Service Account and generating the encryption key
+### Creating a Service Account using the Google Developers Console
-1. From the [Google API Console](, create a [service account](
+1. From the [Google Developers Console](, select your project or create a new one.
-2. Download the generated P12 key.
+2. Under "APIs & auth", click "Credentials".
- IMPORTANT: keep a copy of the key, Google keeps only the public key.
+3. Under "OAuth", click the "Create new client ID" button.
-3. Convert the key to PEM, so we can use it from the Node [crypto]( module.
+4. Select "Service account" as the application type and click "Create Client ID".
+5. The key for your new service account should prompt for download automatically. Note that your key is protected with a password.
+ IMPORTANT: keep a secure copy of the key, as Google keeps only the public key.
+6. Convert the downloaded key to PEM, so we can use it from the Node [crypto]( module.
To do this, run the following in Terminal:
openssl pkcs12 -in downloaded-key-file.p12 -out your-key-file.pem -nodes
- The password for the key is `notasecret`, as mentioned when you downloaded the key from Google.
+ You will be asked for the password you received during step 5.
+That's it! You now have a service account with an email address and a key that you can use from your Node application.
### Granting access to resources to be requested through an API
@@ -248,19 +255,6 @@ For example, to turn on debugging while running the unit tests, use this:
DEBUG=google-oauth-jwt mocha -t 5000
-## Changelog
-* 0.1.2: better integration with `request` providing JWT support in helper methods as well (ex: ``)
-* 0.1.1: re-introduced debugging, now with [debug](
-* 0.1.0: improved documentation, introduced unit tests and refactoring aimed at testability
-* 0.0.7: fixed token expiration check
-* 0.0.6: fixed request function call when using a URI string without options
-* 0.0.5: token now passed using Authorization header (thank you jpd236)
-* 0.0.4: fixed pending callbacks accumulating indefinitely in TokenCache
-* 0.0.3: introduction of TokenCache
-* 0.0.2: improved error handling and documentation
-* 0.0.1: initial version
## Compatibility
+ Tested with Node 0.8

0 comments on commit f3e91c0

Please sign in to comment.