X-BeenThere: fougrapi@googlegroups.com
Received: by 10.150.112.25 with SMTP id k25ls16305ybc.3.p; Wed, 10 Feb 2010 
	21:52:02 -0800 (PST)
Received: by 10.150.119.4 with SMTP id r4mr2533258ybc.24.1265867521953;
        Wed, 10 Feb 2010 21:52:01 -0800 (PST)
Received: by 10.101.195.7 with SMTP id x7mr1106105anp.12.1265867341384;
        Wed, 10 Feb 2010 21:49:01 -0800 (PST)
Received: by 10.101.195.7 with SMTP id x7mr1106104anp.12.1265867341369;
        Wed, 10 Feb 2010 21:49:01 -0800 (PST)
Return-Path: <scono...@gmail.com>
Received: from mail-gx0-f203.google.com (mail-gx0-f203.google.com [209.85.217.203])
        by gmr-mx.google.com with ESMTP id 18si224857yxe.0.2010.02.10.21.49.01;
        Wed, 10 Feb 2010 21:49:01 -0800 (PST)
Received-SPF: pass (google.com: domain of scono...@gmail.com designates 209.85.217.203 as permitted sender) client-ip=209.85.217.203;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of scono...@gmail.com designates 209.85.217.203 as permitted sender) smtp.mail=scono...@gmail.com
Received: by mail-gx0-f203.google.com with SMTP id 27so1753328gxk.10
        for <fougrapi@googlegroups.com>; Wed, 10 Feb 2010 21:49:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.176.5 with SMTP id y5mr133155ybe.5.1265867341329; Wed, 10 
	Feb 2010 21:49:01 -0800 (PST)
Date: Wed, 10 Feb 2010 21:49:01 -0800 (PST)
In-Reply-To: <995a6740-770f-4c17-8a06-3cd25a099a62@b36g2000pri.googlegroups.com>
X-IP: 24.5.42.138
References: <995a6740-770f-4c17-8a06-3cd25a099a62@b36g2000pri.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-US) 
	AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.260.0 Safari/532.5,gzip(gfe),gzip(gfe)
Message-ID: <6abf335a-ac5a-4f46-9961-d5e8b261fdcc@b36g2000pri.googlegroups.com>
Subject: Re: Changes to sending authenticated requests to Google Reader
From: Steve Conover <scono...@gmail.com>
To: Friends of the Unofficial Google Reader API <fougrapi@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

We use Google Reader to get access to the scrubbed / canonicalized
Atom feeds.  Could you please discuss how to access this capability
without ClientLogin (or any login or that matter)?

This is an extremely valuable tool and it would be a real shame
(somewhat debilitating, in fact) if it went unsupported.  We'd really
like some way to get at this without requiring GUI interaction with a
real user.

Regards,
Steve

On Feb 10, 4:12=A0pm, Brad Hawkes <bhaw...@google.com> wrote:
> Hello friends,
>
> We just wanted to let you know about changes coming for Reader
> authentication. We will be changing the details for how our normal web-
> browsing experience handles authentication. This change will break
> clients that are based on using the SID cookie to communicate with
> Reader (this seems to be many current clients). To ensure that your
> app continues to be able to access Reader data you should transition
> to using ClientLogin to access Reader. This is the general mechanism
> that is preferred for communication with many Google services. Details
> of how to use ClientLogin, along with some libraries that are
> available:http://code.google.com/apis/gdata/docs/auth/clientlogin.html
>
> Here is a quick summary of how to make this change:
> For those apps that area already obtaining authentication fromhttps://www=
.google.com/accounts/ClientLoginyou should get back as
> part of your response an Auth=3D value. For every request you send to
> Reader you should provide that value as a HTTP header and things will
> work as usual.
> The header format is: Authorization:GoogleLogin auth=3D[value obtained
> from ClientLogin]
>
> Also please keep in mind that both SID cookies and Auth tokens do
> expire. You should store your Auth token, but if you start to get 401
> errors you may need to obtain a new Auth token. You should not do
> retries on 401 errors unless you have obtained a new Auth token.
>
> Thanks for your attention.
>
> Brad Hawkes
> Google Reader Team