On Wednesday, August 5, 2015 at 1:26:16 AM UTC+8, Nikolaus Rath wrote:
>
> On Aug 04 2015, Chris Wayg <[email protected] <javascript:>> wrote:
> > s3ql documentation mentions* S3-like
> > authentication*, but I can't seem to find this on the Google site. Has
> that
> > been discontinued?
>
> No, it still works fine for me. Are the links in the first bullet point
> of http://www.rath.org/s3ql-docs/backends.html#google-storage not
> working for you?
>
Elsewhere on the site Google states that only OAuth is supported, so when I
followed the first link and saw it was about 'Migration', I thought it was
not what I was looking for. Upon looking it up again and scrolling down
further I found the info you were pointing to.
>
> > The docs state: "...you need to use oauth2 as the backend login, and a
> > valid OAuth2 refresh token as the backend password.
> > To obtain a refresh token, you can use the s3ql_oauth_client program."
> >
> > So I suppose the ~/.s3ql/authinfo2 file should look something like this:
> >
> > [gs] {?}
> > storage-url: gs{?}://mygooglebucket
> > backend-login: oauth2
> > backend-password: [refresh token] {??}
> > fs-passphrase: my_own_passphrase
>
> Yes.
>
> > I am puzzled as to where I would get the refresh token?
>
> From s3ql_oauth_client.
>
> > I do not have a s3ql_oauth_client script in my version of s3ql on Debian
> > Wheezy, but it is present in Jessie (s3ql 2.11.1). Is oauth2 even
> supported
> > in s3ql 1.11.1?
>
> No.
>
All right so OAuth will only work on Jessie.
Thanks, I was able to get it working on Wheezy with your pointers
using S3-like authentication.
Greetings,
Chris
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
