I apologize in advance for possibly getting wrong the whole subject -
I am quite a newbie in terms of development over twitter :)

It seems to me that once, whenever user needed to authorize certain
application, he was asked to log in via a sign-in page, and then
proceeded to application authorization page. If the user was already
signed in, he proceeded directly to the authorization page. If the
user already authorized the application, but hasn't signed in yet, he
was only asked to sign-in w/o further application authorization.

Now authentication and authorization seem to be coupled in a single

It creates a problem given the user already authorized the
application, and then signed out. Next time the user signs in with
twitter, he gets this "scary" authorization page again.

Am I missing something or is there a reason behind this?


Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 

Reply via email to