On Fri, Sep 3, 2010 at 6:16 AM, Dylan <dy...@theginsburgs.org> wrote:
> I have many thousands of users and one who is reporting a problem I
> can't diagnose. Unfortunately, I don't have detailed information but
> I'm hoping the problem can trigger a suggestion from someone.

> The user is authenticated with ClientLogin which my application
> believes is successful. But then all further requests return 403.

> And that's all I know right now. The user is able to log in with a
> different account so it's not environmental and authentication is
> working for (literally) the other 99.9% of my users. I do handle
> Captcha challenges (which this user isn't reporting) and I had the
> user change their password in the hopes that it would reset a
> challenge flag or something. The user is able to access Google Reader
> through the web. It's probably not relevant but the user is in Israel.
> (I'm grasping here.)

> Any ideas?

> Are you setting the account type to GOOGLE when requesting the auth token
> (HOSTED_OR_GOOGLE is the default, but Reader doesn't support hosted (Google
> Apps for Your Domain) accounts)?

> Mihai

> On Fri, Sep 3, 2010 at 6:16 AM, Dylan <dy...@theginsburgs.org> wrote:
> > I have many thousands of users and one who is reporting a problem I
> > can't diagnose. Unfortunately, I don't have detailed information but
> > I'm hoping the problem can trigger a suggestion from someone.

> > The user is authenticated with ClientLogin which my application
> > believes is successful. But then all further requests return 403.

> > And that's all I know right now. The user is able to log in with a
> > different account so it's not environmental and authentication is
> > working for (literally) the other 99.9% of my users. I do handle
> > Captcha challenges (which this user isn't reporting) and I had the
> > user change their password in the hopes that it would reset a
> > challenge flag or something. The user is able to access Google Reader
> > through the web. It's probably not relevant but the user is in Israel.
> > (I'm grasping here.)

> > Any ideas?

> Use HOSTED_OR_GOOGLE if you're not sure which type of account you want authorization for. If the user information > matches both a hosted and a Google account, only the hosted account is authorized.

> Thanks for replying.

> Yes, I am setting the account type to GOOGLE.

> On Sep 3, 5:30špm, Mihai Parparita <mih...@google.com> wrote:

> > Are you setting the account type to GOOGLE when requesting the auth token
> > (HOSTED_OR_GOOGLE is the default, but Reader doesn't support hosted (Google
> > Apps for Your Domain) accounts)?

> > Mihai

> > On Fri, Sep 3, 2010 at 6:16 AM, Dylan <dy...@theginsburgs.org> wrote:
> > > I have many thousands of users and one who is reporting a problem I
> > > can't diagnose. Unfortunately, I don't have detailed information but
> > > I'm hoping the problem can trigger a suggestion from someone.

> > > The user is authenticated with ClientLogin which my application
> > > believes is successful. But then all further requests return 403.

> > > And that's all I know right now. The user is able to log in with a
> > > different account so it's not environmental and authentication is
> > > working for (literally) the other 99.9% of my users. I do handle
> > > Captcha challenges (which this user isn't reporting) and I had the
> > > user change their password in the hopes that it would reset a
> > > challenge flag or something. The user is able to access Google Reader
> > > through the web. It's probably not relevant but the user is in Israel.
> > > (I'm grasping here.)

> > > Any ideas?