Third party authentications should be removed when Glassware that created authentication is removed

[GoogleCodeExporter]

It would seem that when the application that created the credentials is 
removed/un-authorized, its credentials should be removed from the 
AccountManager.

At the very least be some way for the application to remove the credentials 
from the server (a logout of application, if you would).

Original issue reported on code.google.com by jessie.m...@finicity.com on 8 Jul 2014 at 9:31

[GoogleCodeExporter]

Hello,

Could you clarify what you mean by "removed from the server"? Are you referring 
to the third party's server or Google's?

Regarding the credentials on the device, they should be removed when a 
Glassware is uninstalled. Also, the credentials only transit on Google's server 
only to be sync'ed to the device, they are not stored indefinitely on the cloud.

Best,
Alain

Original comment by ala...@google.com on 9 Jul 2014 at 4:31

• Changed state: Pending
• Added labels: Component-GDK, Priority-Medium

[GoogleCodeExporter]

Mentioning on the device. So, here's the flow that I would imagine:

User logs in to account via Website and Third Party Auth flow. This causes the 
account to be created on the Google Glass device. Then, the user realizes they 
used the wrong account (work vs personal, maybe?) and wishes to log out. 
Currently, as far as I know, the only way to delete the account would be from 
the Glass device itself. There is no "remove" account method in the mirror API. 
So I would not be able to have a Log Out button in the application. About all I 
could do is direct the user back to the Glassware page for uninstall and then 
have them reinstall.

Original comment by jessie.m...@finicity.com on 9 Jul 2014 at 4:35