Google Docs Connector Broke Google Authentication
I had a student grant Zotero permissions to integrate with his Google Docs (he told me he did not try to make this happen, Zotero pushed out a request for him to allow it permission to integrate). When he allowed this, suddenly he was unable to authenticate into any Google product. For example, he showed me what was happening when he clicked "Sign in" on a shared Google document he was viewing, and nothing would happen. He also could not sign in to YouTube via his Google account.
To fix the problem his university IT department had to wipe all his browsers and reinstall them, and he lost all his cookies and saved passwords. I just wanted to report this to let the community know there could be serious problems with Google Docs connector. If it helps, he was on a Mac computer, but this seems to have impacted multiple browsers on his computer, including Safari and Chrome. He was unable to login to Google products until all of his browsers were completely re-installed.
To fix the problem his university IT department had to wipe all his browsers and reinstall them, and he lost all his cookies and saved passwords. I just wanted to report this to let the community know there could be serious problems with Google Docs connector. If it helps, he was on a Mac computer, but this seems to have impacted multiple browsers on his computer, including Safari and Chrome. He was unable to login to Google products until all of his browsers were completely re-installed.
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
Upgrade Storage
(Also, Zotero does not actually push this onto users unprompted, ever. The request is prompted by clicking on the Zotero toolbar in google docs.)
Since his computer has now been wiped and fixed I'm unable to grab any screenshots or do any testing, but at least this bug is now on record, if other similar reports start coming in.