Bug 139088 - Google auth code not sent when trying to login to drive.
Summary: Google auth code not sent when trying to login to drive.
Status: RESOLVED DUPLICATE of bug 101630
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.4.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-20 10:11 UTC by Jordan Dixon
Modified: 2023-04-12 05:55 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jordan Dixon 2020-12-20 10:11:44 UTC
Description:
Hello, I am trying to access the remote google drive and I cannot because each time I try, it asks for 6 digit auth code that I never receive.

Steps to Reproduce:
1. Turn on 2 factor auth on gmail
2. Go to librewriter and go to open remote and choose google drive 
3. Try to sign in.

Actual Results:
Screen signs in but then asks me for a 6 digit authentication code.

Expected Results:
Used a google sign-in or actually sent me a code to use.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
https://ask.libreoffice.org/en/question/98400/libreoffice-access-to-google-drive-asks-for-authentication-6-digit-pin/
Comment 1 [REDACTED] 2020-12-20 11:43:12 UTC
(In reply to Jordan Dixon from comment #0)

> 
> Expected Results:
> Used a google sign-in or actually sent me a code to use.
> 

It is not LibreOffice to send you a 6-digit PIN code. It is Google which sends you the code by means of Google Authenticator App (https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=de&gl=US) (or alternatively  by SMS - as far as I understand). But even if you install the app and provide the code - it will not work and complain about an invalid device. In fact the real bug is addressed in bug report tdf#101630.
Comment 2 Julien Nabet 2020-12-20 13:05:41 UTC

*** This bug has been marked as a duplicate of bug 101630 ***