[Libreoffice-bugs] [Bug 101630] Google Drive two-factor authentication (2FA) not working again

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=101630

--- Comment #61 from Pedro <vermelhusco1904 at gmail.com> ---
Just an FYI. In the "This week in KDE" of May 15th 2020 Nate Ingraham reported
that a similar issue to this one was solved for KMail and Kontacts.

This is their bug report:
https://bugs.kde.org/show_bug.cgi?id=404990

In comment 122 from that bug report they state the following:

<<Google has approved KMail access to Gmail via Googla Sign-in today, so it
should work again. Should you still see some errors, please let us know.>>

They link to a Reddit topic where a lot of the steps to fix this are detailed!
https://www.reddit.com/r/kde/comments/gi5bol/kmailkontact_oauth_signin_with_gmail_enabled_again/

Here are the relevant comments:

"Hi all,

I would like to share some news :) This morning Google has approved our
verification request to allow KMail/Kontact to sign into Gmail using the Google
Sign In, which supports 2FA out-of-the-box and is more secure, since
KMail/Kontact never sees your password.

If you have your IMAP account in KMail already configured in KMail and you
would like to start using the OAuth sign-in, go to the account configuration
(Settings→Configure KMail→Accounts→Receiving→[your Gmail IMAP account]→Modify)
and in the Advanced tab select "Gmail" in the Authentication combo box.

If you want to add a new account, the Gmail authentication method will be
chosen automatically by KMail.

I apologize it took so long to make Gmail login work again. The bureaucracy
that had to be sorted out in order to comply with Google usage policies was
non-trivial and I'll admit then whenever I had some spare time to work on KDE,
I usually chose to write some code rather than read legal documents and write
privacy policy...

Should you still see "Sign in with Google temporarily disabled for this app" or
some other error, let me know, please."

"Nothing was wrong with KMail really, but if any application wants to access
Gmail through OAuth, it needs to request access to this part of API from
Google. Google considers Gmail to be a "restricted" scope and applications
needs to pass verification and satisfy some extra requirements to get access to
it. So there's a manual process of submitting the application for verification,
writing a dedicated privacy policy, having numerous rounds with Google support
to clear things app and making sure everything is aligned with their terms and
policies for accessing the restricted scopes - it might be fun for a lawyer,
but it certainly isn't the kind of activity a programmer would want to do in
their spare time... :)"

Here's more detail to satisfy Google's requirements to link to Gmail:
https://support.google.com/cloud/answer/9110914?hl=en

Additional Requirements for Specific API Scopes:
https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes

Example of privacy policy that Google requires:
https://community.kde.org/KDE_PIM/Privacy_Policy


Hopefully this is enough information for work to be done to fix this bug. It's
worth research how this works for Microsoft's One Drive as well since that one
is also broken.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20200516/52b9dcee/attachment.htm>