From d9d7597e7d556fd4c59204292a9d057c22a6a0bb Mon Sep 17 00:00:00 2001 From: Thomas Darde Date: Fri, 10 Feb 2017 15:35:49 +0100 Subject: [PATCH 1/2] Update Migrating guide Migrating from 0.8 to 0.9 has been an extremely painful process, I will also add a full sample for using Google::Auth::ServiceAccountCredentials --- MIGRATING.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MIGRATING.md b/MIGRATING.md index bbbbe242c..4c35e3794 100644 --- a/MIGRATING.md +++ b/MIGRATING.md @@ -61,6 +61,8 @@ are expected to be added by end of Q2 2015. The underlying [Signet](https://github.com/google/signet) is still used for authorization. OAuth 2 credentials obtained previously will continue to work with the `0.9` version. OAuth 1 is no longer supported. +If your where using a PKCS12 file to authorize, we recommend you to use a client_secret.json file with googleauth. + ## Media uploads Media uploads are significantly simpler in `0.9`. From 1ad141162cede12ebd1249984417f5a11296b4a9 Mon Sep 17 00:00:00 2001 From: Thomas Darde Date: Sun, 12 Feb 2017 15:02:53 +0100 Subject: [PATCH 2/2] Update MIGRATING.md --- MIGRATING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MIGRATING.md b/MIGRATING.md index 4c35e3794..7317816b1 100644 --- a/MIGRATING.md +++ b/MIGRATING.md @@ -61,7 +61,7 @@ are expected to be added by end of Q2 2015. The underlying [Signet](https://github.com/google/signet) is still used for authorization. OAuth 2 credentials obtained previously will continue to work with the `0.9` version. OAuth 1 is no longer supported. -If your where using a PKCS12 file to authorize, we recommend you to use a client_secret.json file with googleauth. +If you were using a PKCS12 file to authorize, we recommend you generate a new key for the service account using the JSON format ( client_secret.json) file with googleauth. ## Media uploads