Consider the scenario where the user is taken to the google's
"authorize token" page and use denies the access.

== 1 ==
The documentation <http://code.google.com/apis/accounts/docs/
OAuth.html> says -
1. If the user denies access, they are redirected to a Google page
      (see example      <http://code.google.com/apis/accounts/images/
accessdenypage.jpg>).
   2. If the user grants access, the referenced request token is
      immediately authorized. If a callback URL is provided, Google
      redirects the user to the URL specified in the web application
      registration. If no callback URL is provided, Google displays a
      simple message to the user: "The token has been authorized."

== 2 ==

Until few days back -

The user was redirected from "authorize token" page as follows:

If access granted,  user was redirected to
{callback_url}?oauth_token={authorized_request_token}
If access denied, user was redirected to {callback_url} without any
parameters.

This is how I used to distinguish between the two events in my
application and had written the flow as per that.

== 3 ==
Now -

The user is being redirected from "authorize token" page as follows:

If access granted,  user was redirected to
{callback_url}?oauth_token={authorized_request_token}
If access denied, user was redirected to
{callback_url}?oauth_token={UNauthorized_request_token}.

So I have to actually make a request to fetch access token in order to
check if the previously returned oauth_token is authorized request
token or unauthorized request token.

Not only this is inconsistent with the documentation, it is certainly
not a better way of doing it. In my opinion, the previous
implementation (==2== above) was the best was to deal with it.

Is there anyway of posting a bug to google regarding this issue?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OAuth" 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/oauth?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to