or Create a profile
17 Feb, 2011 12:18 AM
I've recently run into a situation where I installed a2c on a pc
that I was using frequently, but no longer have access to. It would
be nice to have a way to permanently revoke the link between a2c
and one or many of the attached chrome instances. I took a peak
through the settings in both the extension and the app, and I don't
really see anything that seems to apply. I realize that I can
rename the "identifier" which would in theory no longer push links
to the "incorrectly" named chrome instances, but it would be great
if there was a mechanism that listed authorized chrome instances.
If possible it would be preferable to access this list from within
the a2c app itself rather than the chrome extension so that only
the device owner could access the "deauthorization" options.
on 17 Feb, 2011 03:33 AM
This is an interesting suggestion. I can't deny the appeal of
it, but I'm having trouble figuring out exactly how I would go
about implementing it.
As it is, you "Authorize" the app as a whole to use your account
as an identifier through OAuth. You can revoke access to all of
your instances by using the [Revoke Access] link next to
android2cloud at https://www.google.com/accounts/b/0/IssuedAuthSubTokens
At the moment, though, there's no way to deauthorise a specific
client other than to deauthorise everything, then authorise the
ones you want to again. And I'm not sure it's even feasible to
authorise/deauthorise on a per-client scale.
Sorry, wish I had better news.
Formatting help /
(switch to plain text)
(switch to Markdown)
You can attach files up to 10MB
If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.
A conversation has been started with the The 2cloud Project staff to resolve this discussion.
This discussion is private.
Only you and The 2cloud Project support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
You can use Command ⌘ instead of Control ^ on Mac
Powered by Tender™.