On Thu, Jan 19, 2012 at 12:40 PM, Kookamonga wrote:
Oh well, still no satisfactory answer. (To tell you the truth, I don't
understand the "broadcast receiver" answer... )
You only get what you pay for :) There's two sides of the OAuth token
story: server side and Android (AccountManager) side. You can revoke
access you've granted to apps here, it's not just for Chrome-to-phone,
and just for Android apps, but Web, etc. as well:
https://www.google.com/accounts/IssuedAuthSubTokensOn Android, when you call AccountManager.getAuthToken() you will be
presented with a screen saying something like 'Application foo wants to
access your Google Reader auth tokens'. If you click 'Allow', AccountManager
will insert a line in its database with the UID of your app, thus granting
you access to those tokens. Next time you call getAuthToken(), there
will be no confirmation screen, since you already have the necessary
permission. For example, this line means that the app with UID 10062
has access to Google Reader tokens from account 1 (your primary
Google account)
.schema grants
CREATE TABLE grants ( accounts_id INTEGER NOT NULL, auth_token_type STRING NOT
NULL, uid INTEGER NOT NULL, UNIQUE (accounts_id,auth_token_type,uid));
1|reader|10062
There is currently now way to revoke that permission
(i.e., delete the line from the DB using a public API).
However (*I think*), if you uninstall the app, the AccountManager
will be notified and delete your app from the grants DB,
effectively revoking access.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
