Dear Paul,
Until we upgrade the access token we are able to link the
same profile again. If I try to link another profile it throws the
exception. In my case I was upgrading the access token as soon as i
got it from the callback url. So I was getting that error.
But it would have been better as you suggest, if we can get the
exception in the call back url itself, instead of displaying it there.
Cheers!
Krish
On Jan 27, 10:12 am, Krish <[email protected]> wrote:
> Dear Paul,
>
> I tried to reproduce the same in oauth playground, it
> work fine over there. Probably I might be missing some thing. Waiting
> for your reply.
>
> Thanks,
> Krish
>
> On Jan 26, 11:41 pm, "Paul (Google)" <[email protected]> wrote:
>
> > Hi Krish,
>
> > Thanks for following up! With the current OAuthAuthorizeToken service,
> > I can't think of a good way to prevent users from seeing theerrorif they
> > use their browserbackbuttons. Most browsers compensate for a HTTP
> > redirect or HTML meta refresh by not including the page with the
> > redirect/refresh in the browser history, so my previous suggestion probably
> > wasn't good. If you get newrequesttokens for users on your callback page,
> > they will still be sending the old ones to the service if they hit their
> > browserbackbuttons (thetokenis in the URL).
>
> > I'll do some research to see why the OAuthAuthorizeToken page doesn't send
> > anerrorto the callback URL instead of displaying it to the user. This
> > seems like it would solve the issue, but there might be an argument I'm
> > overlooking for not doing this.
>
> > Thanks again!
>
> > Paul
--
You received this message because you are subscribed to the Google Groups
"Google Health Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/googlehealthdevelopers?hl=en.
