X-BeenThere: fougrapi@googlegroups.com Received: by 10.114.33.26 with SMTP id g26ls984961wag.3.p; Mon, 08 Feb 2010 19:35:25 -0800 (PST) Received: by 10.115.80.10 with SMTP id h10mr1458238wal.7.1265686525808; Mon, 08 Feb 2010 19:35:25 -0800 (PST) Received: by 10.115.80.10 with SMTP id h10mr1458237wal.7.1265686525788; Mon, 08 Feb 2010 19:35:25 -0800 (PST) Return-Path: Received: from email.corp.newsgator.com (email.corp.newsgator.com [38.97.237.160]) by gmr-mx.google.com with ESMTP id 16si1312274pxi.1.2010.02.08.19.35.25; Mon, 08 Feb 2010 19:35:25 -0800 (PST) Received-SPF: pass (google.com: domain of bre...@newsgator.com designates 38.97.237.160 as permitted sender) client-ip=38.97.237.160; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of bre...@newsgator.com designates 38.97.237.160 as permitted sender) smtp.mail=bre...@newsgator.com Received: from MSG1.corp.newsgator.com ([10.0.8.224]) by msg1 ([10.0.8.224]) with mapi; Mon, 8 Feb 2010 20:35:24 -0700 From: Brent Simmons To: "fougrapi@googlegroups.com" Date: Mon, 8 Feb 2010 20:35:24 -0700 Subject: Re: Authentication suddenly failing Thread-Topic: Authentication suddenly failing Thread-Index: AcqpOOnYP6yQ3Bx5SN6JMky4xJTvTA== Message-ID: <8D16144E-0EC1-4999-A992-5035AA81ACCD@newsgator.com> References: <5FD34CF9-1E24-4E2C-B47F-DBC2F7D8BBC6@newsgator.com> <264cf901002081930m37299bf4i3be6b6a9cfd6695@mail.gmail.com> In-Reply-To: <264cf901002081930m37299bf4i3be6b6a9cfd6695@mail.gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Thanks, Mihai. I'm hoping, of course, that it'll just start working again. I don't mind ma= king changes to apps, it's just that with iPhone apps there's a delay as th= ey go through Apple's approval process. -Brent On Feb 8, 2010, at 7:30 PM, Mihai Parparita wrote: > Hi Brent, >=20 > This is an unintended change as part of a recent Reader push. We're > still investigating what changed and what (if anything) third-party > clients have to do. We'll let you know as soon as we have a solution. >=20 > Mihai >=20 > On Mon, Feb 8, 2010 at 10:26 PM, Brent Simmons wro= te: >> I'm getting widespread reports tonight that people can't login via NetNe= wsWire. I checked it out myself and have the same problem. >>=20 >> Calling /accounts/ClientLogin works perfectly. I get back a 200 status c= ode and Auth, LSID, and SID strings. >>=20 >> Then I got to fetch the T token, via /reader/api/0/token, passing back S= ID via the Cookie header -- and I always get back a 403. >>=20 >> Other people seeing this? Any idea what's going on, or how to get back u= p and running? >>=20 >> -Brent