Bug 101630 - Google Drive two-factor authentication (2FA) not working again
Summary: Google Drive two-factor authentication (2FA) not working again
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.2.0.4 release
Hardware: All All
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 100914 119511 123315 124291 124375 124439 126212 127662 129835 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-08-21 02:47 UTC by Leandro Martín Drudi
Modified: 2020-02-10 07:06 UTC (History)
30 users (show)

See Also:
Crash report or crash signature:


Attachments
Start login (23.79 KB, image/png)
2016-08-21 02:47 UTC, Leandro Martín Drudi
Details
Error... The same error as before (11.67 KB, image/png)
2016-08-21 02:48 UTC, Leandro Martín Drudi
Details
LibreOffice 5.2.0.4 Google drive 2FA failing english (20.72 KB, image/png)
2016-09-02 12:19 UTC, Shrenik
Details
First screen grab for comment 7 (84.68 KB, image/jpeg)
2016-09-28 13:41 UTC, Bob Harvey
Details
Second screen grab for comment 7 (140.87 KB, image/png)
2016-09-28 13:43 UTC, Bob Harvey
Details
screen of the issue in ubuntu (32.63 KB, image/png)
2018-05-14 16:16 UTC, Cristiano
Details
PopUp in my Android Smartphone. Android 8.0 (48.40 KB, image/png)
2018-09-24 23:54 UTC, Leandro Martín Drudi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leandro Martín Drudi 2016-08-21 02:47:21 UTC
Created attachment 126925 [details]
Start login

In the new version this bug is not corrected (Bug 100113).
Now he asks for a PIN but never gets a message that does not accept PIN and the PIN generated by Autenticator App.
Comment 1 Leandro Martín Drudi 2016-08-21 02:48:25 UTC
Created attachment 126926 [details]
Error... The same error as before
Comment 2 Cor Nouws 2016-08-22 09:27:04 UTC
@guiseppe: maybe you can have a look?
thanks!
Comment 3 Giuseppe Castagno (aka beppec56) 2016-08-23 10:39:34 UTC
Checked with:

Version: 5.2.0.4
Build ID: 066b007f5ebcc236395c7d282ba488bca6720265
CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; 
Locale: it-IT (it_IT)

I found it working on standard (e.g. not 2FA) account.
Unfortunately not working on a 2FA enabled account.
Strangely Google sent me always the same PIN code.

Until a few days ago 2FA worked, with the same LO version.
I think Google changed again the login page.

Unfortunately I don't have time to look into the matter ATM, it will be necessary to fix something in libcmis I think.
Comment 4 Aron Budea 2016-08-24 02:13:56 UTC
Confirmed based on Giuseppe's reply.
Comment 5 Shrenik 2016-09-02 12:19:26 UTC
Created attachment 127123 [details]
LibreOffice 5.2.0.4 Google drive 2FA failing english

Have experienced the same "Error saving the document <filename>: The specified device is invalid" error as before. The only advancement with 5.2.0.4 is that we are now being requested the PIN. But once we enter that, the result remains the same as in the screenshot attached.
Comment 6 Alberto Gaburro 2016-09-15 13:04:57 UTC
Same problem on Libreoffice 5.2.1.2 x64 on Windows 10.

After entering the PIN, I get the error "The specified device is invalid".
So I can't even browse my contents on Google Drive.
Comment 7 Bob Harvey 2016-09-28 13:39:34 UTC
I am not sure if my experience is appropriate to this bug, or if it something else.

But it is definitely a case of 2-factor not working!

I have installed the 64 bit version 5.2.2.2

When attempting to connect to google drive I get a dialogue asking me for a PIN from my account   There is a small dialgoue with a G- in front of the data entry box.

What pops up on my phone is a wholly different dialogue, asking me to tap on one of 3 numbers that are displayed on the login attempt.  They aren't.

So LibreOffice is asking for a number that is not displayed on the phone, and the phone is asking for a number that is not displayed by LibreOffice.  SOme mistake there, I feel.

Screen grabs wil follow
Comment 8 Bob Harvey 2016-09-28 13:41:50 UTC
Created attachment 127700 [details]
First screen grab for comment 7

This is Libre Office trying to log into my Google Drive account, and waiting for authentication
Comment 9 Bob Harvey 2016-09-28 13:43:36 UTC
Created attachment 127701 [details]
Second screen grab for comment 7

This is what the phone offers as the 2nd factor
Comment 10 Alberto Gaburro 2016-10-21 09:43:41 UTC
(In reply to Alberto Gaburro from comment #6)
> Same problem on Libreoffice 5.2.1.2 x64 on Windows 10.
> 
> After entering the PIN, I get the error "The specified device is invalid".
> So I can't even browse my contents on Google Drive.

Upgraded Libreoffice from 5.2.1.2 to 5.2.2.2 x64 on Windows 10.
Nothing changes :(
Comment 11 Alberto Gaburro 2016-11-04 15:58:52 UTC
(In reply to Alberto Gaburro from comment #10)
> (In reply to Alberto Gaburro from comment #6)
> > Same problem on Libreoffice 5.2.1.2 x64 on Windows 10.
> > 
> > After entering the PIN, I get the error "The specified device is invalid".
> > So I can't even browse my contents on Google Drive.
> 
> Upgraded Libreoffice from 5.2.1.2 to 5.2.2.2 x64 on Windows 10.
> Nothing changes :(

Upgraded Libreoffice from 5.2.2.2 to 5.2.3.3 x64 on Windows 10.
Nothing changes :(
Comment 12 vinixda 2017-01-29 11:38:58 UTC
I can confirm that Google Drive 2FA is broke again. 

LibreOffice 5.2.4.2 (Fresh PPA), Linux Mint 18.1.
Comment 13 Alberto Gaburro 2017-02-01 08:39:27 UTC
(In reply to Alberto Gaburro from comment #11)
> (In reply to Alberto Gaburro from comment #10)
> > (In reply to Alberto Gaburro from comment #6)
> > > Same problem on Libreoffice 5.2.1.2 x64 on Windows 10.
> > > 
> > > After entering the PIN, I get the error "The specified device is invalid".
> > > So I can't even browse my contents on Google Drive.
> > 
> > Upgraded Libreoffice from 5.2.1.2 to 5.2.2.2 x64 on Windows 10.
> > Nothing changes :(
> 
> Upgraded Libreoffice from 5.2.2.2 to 5.2.3.3 x64 on Windows 10.
> Nothing changes :(

Upgraded Libreoffice from 5.2.4.2 to 5.2.5.1 x64 on Windows 10.
Nothing changes :(
Comment 14 gijs 2017-02-04 16:13:25 UTC
Upgraded Libreoffice to 5.3.0.3 x64 on Windows 10.
Nothing changes :(
Comment 15 Aron Budea 2017-02-04 20:37:59 UTC
Version field is supposed to be the oldest version the bug was observed with, please don't change to a newer one.
Comment 16 blendergeek 2017-02-25 18:36:42 UTC
Just confirmed on XUbuntu 16.04.2 using the following LibreOffice build:
Version: 5.3.0.3
Build ID: 1:5.3.0~rc3-0ubuntu1~xenial1.1
CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; VCL: gtk2; Layout Engine: new; 
Locale: en-US (en_US.UTF-8); Calc: group

Further, I noticed that when I enter a wrong password with two-factor enabled, the dialogue for two factor appears. Then I enter the six digit code and whatever I enter in that box I get "The specified device is invalid".

I also get this error if I type an unused email address or the wrong password.
Comment 17 Robert Cabane 2017-04-01 07:34:22 UTC
Same behavior here (using LO from TDF, version 5.3.1.2). In fact, my phone never receives the expected SMS from Google, so I can't even type the 6-digit G-code.
Comment 18 Max S. 2017-04-27 12:41:55 UTC
I confirm the bug in version 5.2.6.2 on Windows 10 x64.
2-FA enabled Google Account doesn't work.
Comment 19 Robert Cabane 2017-04-27 14:13:38 UTC
Just the same, LO from TDF, 5.3.2.2, Linux
Comment 20 Aron Budea 2017-04-27 15:52:45 UTC
Thanks for the update, but Max, please keep version at earliest (known) affected.
Comment 21 Alois Hammer 2017-05-10 02:46:48 UTC
Confirmed "The specified device is invalid." with good credentials and good OATH-TOTP code.

Let me know if I can add any information. It's not clear to me how or whether it's possible to enable any form of logging for LibreOffice on Windows.

Version: 5.3.2.2 (x64)
Build ID: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1
CPU Threads: 8; OS Version: Windows 6.1; UI Render: GL; Layout Engine: new; 
Locale: en-US (en_US); Calc: group

Oracle JRE 1.8.0_131 x86 and x64 installed system-wide, functioning, and enabled in LO options.

Java critical files -

C:\Windows\Sun\Java\Deployment\deployment.config -

deployment.system.config=file:///C:/Windows/Sun/Java/Deployment/deployment.properties
deployment.system.config.mandatory=true
deployment.system.config.locked
deployment.system.config.mandatory.locked


C:\Windows\Sun\Java\Deployment\deployment.properties -

#System Deployment Properties
deployment.cache.jarcompression.locked=true
deployment.cache.jarcompression=9
deployment.cache.max.size.locked=true
deployment.cache.max.size=256
deployment.console.startup.mode.locked=true
deployment.console.startup.mode=DISABLE
deployment.expiration.check.enabled.locked=true
deployment.expiration.check.enabled=false
deployment.insecure.jres.locked=true
deployment.insecure.jres=NEVER
deployment.javaws.associations.locked=true
deployment.javaws.associations=2
deployment.javaws.shortcut.locked=true
deployment.javaws.shortcut=ASK_USER
deployment.javaws.update.timeout.locked=true
deployment.javaws.update.timeout=2500
deployment.log.locked=true
deployment.log=false
deployment.proxy.type.locked=true
deployment.proxy.type=0
deployment.roaming.profile.locked=true
deployment.roaming.profile=false
deployment.security.authenticator.locked=
deployment.security.authenticator=true
deployment.security.level.locked=true
deployment.security.level=VERY_HIGH
deployment.security.revocation.check.locked=true
deployment.security.revocation.check=ALL_CERTIFICATES
deployment.security.SSLv3.locked=true
deployment.security.SSLv3=false
deployment.security.use.native.sandbox.locked=true
deployment.security.use.native.sandbox=true
deployment.security.validation.clockskew.locked=true
deployment.security.validation.clockskew=5
deployment.security.validation.crl.locked=true
deployment.security.validation.crl=true
deployment.security.validation.ocsp.locked=true
deployment.security.validation.ocsp=true
deployment.security.validation.timeout.locked=true
deployment.security.validation.timeout=5
deployment.trace.locked=true
deployment.trace=false
deployment.user.logdir.locked=true
deployment.user.logdir=null
install.disable.sponsor.offers.locked=true
install.disable.sponsor.offers=true
Comment 22 Oliver Brinzing 2017-05-14 08:03:45 UTC
Today i tried to connect to Google Drive with LO 5.3.3(32Bit) on Win10Pro 64Bit with 2FA, and i worked, but only, if i receive the PIN via SMS on my IPhone.
During the initial installation i received 2 PINs.

PIN via Autenticator App does not work for me too.
Comment 23 Leandro Martín Drudi 2017-05-14 14:14:42 UTC
[ES]
Yo no recibo nunca el mensaje con Movistar en Argentina. Si es para ingreso al Mail, sí, pero no para esto.
[EN]
I never receive the message with Movistar in Argentina. If it is to login to the Mail, yes, but not for this.
Comment 24 Sergejs Ušakovs 2017-08-15 09:50:04 UTC
For me also, authentication via Google Authenticator app on iOS didn't work.
As LO - strangely - doesn't offer a choice of alternative options to choice Google authentication code delivery method delivery, then you have to setup your phone as Default Google Authentication option - then, again problem, as Google, doesn't allow freely to choose delivery option, and set default delivery option itself, the only way to get phone as a default Google authenticator code delivery option is to remove all other options, namely, in my case, Google Prompt option, and Google Authenticator app option.
Then - again strangely - LO ask for GDrive credentials, incl. authenticator code again - I am just wondering, what the sense of going such loop..?

Then, when finally Gdrive directory get populated there are only just like 50-100 files and one directory, out of 1000s... - rendering it unusable.

LO Version: 5.4.0.3
Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c
CPU threads: 2; OS: Windows 6.2; UI render: default; 
Locale: en-IE (en_US); Calc: group
Comment 25 Robert Cabane 2017-08-15 10:33:12 UTC
I tried to connect to Google Drive just after having installed LO 5.4. No change appeared : my phone received non SMS from Google.
Comment 26 Miloš Jovanović 2018-01-23 12:42:49 UTC
Using LO 5.4.4.2 on Ubuntu 17.10, with 2FA *disabled*, I am asked for the PIN anyway. Unable to sign in.
Comment 27 Karl Foley 2018-02-04 11:53:40 UTC
Experiencing the same issue in Windows 6.0.0.3.
Comment 28 Robert Cabane 2018-03-02 07:41:12 UTC
The bug is still there on LO 6.0.4 (Linux). I tried opening Google drive giving my account either as (my Gmail address) or (the first part of my Gmail address), without success : my phone didn't receive any SMS.
Comment 29 Leandro Martín Drudi 2018-03-02 17:47:29 UTC
With Outlook. com accounts. the same thing happens.
Is another report required or can you see with this one as well?
With Outlook. com basins, the generated URL generates the same error.
Comment 30 Leandro Martín Drudi 2018-03-02 17:48:28 UTC
(In reply to Leandro Martín Drudi from comment #29)
> With Outlook. com accounts. the same thing happens.
> Is another report required or can you see with this one as well?
> With Outlook. com basins, the generated URL generates the same error.

Sorry, Basins*: Accounts
(I translate with google)
Comment 31 farside268 2018-03-10 01:22:20 UTC
This is still a problem in 6.0.2.1. I have 2FA enabled and get the phone notification to approve the login every time I try to login. I approve the login, which does nothing with LO. I try to enter the PIN from Authenticator and receive the message about the device being invalid.
Comment 32 Aron Budea 2018-03-10 04:08:27 UTC
Let's keep version field as the earliest known affected version.
Comment 33 Chris 2018-03-30 15:16:32 UTC
This bug also affects 2FA Google accounts that are using the App Password feature (https://support.google.com/accounts/answer/185833?hl=en) This is a feature that allows you to use a 16 character password that is unique to the app and it usually bypasses the need for any other 2FA method.  Whether you use the standard Google password or the App password, LibreOffice is still prompting for a G-Pin to complete the sign in.
Comment 34 Cristiano 2018-05-14 16:16:26 UTC
Created attachment 142096 [details]
screen of the issue in ubuntu

I'm using the version  6.0.3.2 with Ubuntu (Build ID: 1:6.0.3-0ubuntu1).

I was able to setup my google account in order to receive the 6-digits PIN in my smartphone. 
But even after type it I'm getting the "The specified device is invalid." when trying to setup the connection.

Btw, I'm able to connect to Drive using Nautilus.
Comment 35 Drew Jensen 2018-08-26 17:16:41 UTC
*** Bug 119511 has been marked as a duplicate of this bug. ***
Comment 36 Robert Cabane 2018-09-24 20:46:57 UTC
Hello, I just updated my LO install to the 6.1.1 version (Linux + KDE). And, suddenly, the connection with my Google drive works (with 2FA), that's really marvelous !
Thank you for your work.
Comment 37 Leandro Martín Drudi 2018-09-24 20:50:23 UTC
I try in Windows and don't work.
Versión: 6.1.1.2 (x64)
Id. de compilación: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b
Subprocs. CPU: 4; SO: Windows 10.0; Repres. IU: predet.; 
Configuración regional: es-AR (es_AR); Calc: CL
Comment 38 Xisco Faulí 2018-09-24 23:43:45 UTC
(In reply to Robert Cabane from comment #36)
> Hello, I just updated my LO install to the 6.1.1 version (Linux + KDE). And,
> suddenly, the connection with my Google drive works (with 2FA), that's
> really marvelous !
> Thank you for your work.

Most likely fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-6-1-1&id=2751f625990bc4d619eb2b0b895f9d510f768a02
Comment 39 Xisco Faulí 2018-09-24 23:44:09 UTC
(In reply to Leandro Martín Drudi from comment #37)
> I try in Windows and don't work.
> Versión: 6.1.1.2 (x64)
> Id. de compilación: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b
> Subprocs. CPU: 4; SO: Windows 10.0; Repres. IU: predet.; 
> Configuración regional: es-AR (es_AR); Calc: CL

Do you get any erro message?
Comment 40 Leandro Martín Drudi 2018-09-24 23:52:58 UTC
(In reply to Xisco Faulí from comment #39)
> (In reply to Leandro Martín Drudi from comment #37)
> > I try in Windows and don't work.
> > Versión: 6.1.1.2 (x64)
> > Id. de compilación: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b
> > Subprocs. CPU: 4; SO: Windows 10.0; Repres. IU: predet.; 
> > Configuración regional: es-AR (es_AR); Calc: CL
> 
> Do you get any erro message?

[ES]
El mismo de siempre: «El dispositivo especificado no es válido.»
Cuando he confirmado el LogIn en la ventana de LibreOffice, una ventana aparece en mi spartphone pidiendo autorización para el LogIn (con el fin de no usar el código).
Presione "OK" o presione "No, no soy yo", igualmente, el código no funciona. He probado con el que llega por SMS tanto como el que se genera con la App "Autenticator" y ninguna funciona. El resultado es siempre el mismo.

[EN]
The same like always: "The specified device is invalid."
When I have confirmed the LogIn in the LibreOffice window, a window appears on my spartphone asking for authorization for the LogIn (in order not to use the code).
Press "OK" or press "No, it's not me", likewise, the code does not work. I have tried with the one that arrives by SMS as much as the one generated with the "Authenticator" App and none of them work. The result is always the same.
Comment 41 Leandro Martín Drudi 2018-09-24 23:54:12 UTC
Created attachment 145146 [details]
PopUp in my Android Smartphone. Android 8.0
Comment 42 Oliver Brinzing 2018-09-25 07:14:14 UTC
it's not working  with

Version: 6.1.2.1 (x64)
Build-ID: 65905a128db06ba48db947242809d14d3f9a93fe
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc:

and Authenticator App. 
Entering 6 digit code ends with error message:
"The specified device is invalid."

browser login with Authenticator App works on my notebook.
Comment 43 Karl Foley 2018-10-20 07:31:18 UTC
Still getting this in Linux 6.1.2.1 on Ubuntu 18.10.
Trying to use remote storage with 2FA application on phone.
Program prompts for pin, no popup on phone, pin from app results on "Invaid Device" message.
Comment 44 Aron Budea 2018-10-22 05:17:26 UTC
Thanks for checking, Karl, please note that the version field is for the oldest known affected version.
Comment 45 ATX 2018-10-31 20:53:29 UTC
This is not working for 6.1.2.1 and 6.2.0.0.alpha1 on W10.

Issues:
- 6 digit code asked with and without 2FA enabled.
- Invalide device error message.
Comment 46 Warren Downs 2018-12-14 00:01:23 UTC
Same problem on LibreOfficeDev 6.2.0.0.beta1
Tried without 2FA, got prompt for 6 digit code.
Turned on 2FA, installed Google Authenticator, but code from Authenticator does not work.
Comment 47 Miloš Jovanović 2018-12-14 12:04:03 UTC
To add onto what was previously written. 

PIN is asked for irrespective of 2FA status.

Not using Authenticator, the 2FA SMS is not sent either.

Would happily volunteer my time to debug, but the information on https://wiki.documentfoundation.org/QA/BugReport/Debug_Information is daunting. Would need a bit of guidance.

Build ID: 1:6.1.3~rc2-0ubuntu0.18.04.2
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group threaded
Comment 48 Xisco Faulí 2018-12-14 12:11:41 UTC
@Muhammet, since you fixed the personas issue, I thought you might be interested in this issue as well. I know they are not related at all, I'm just trying to find someone who might fix this one...
Comment 49 Oliver Brinzing 2019-02-11 17:31:34 UTC
*** Bug 123315 has been marked as a duplicate of this bug. ***
Comment 50 Oliver Brinzing 2019-03-23 16:09:06 UTC
*** Bug 124291 has been marked as a duplicate of this bug. ***
Comment 51 Oliver Brinzing 2019-03-27 19:50:11 UTC
*** Bug 124375 has been marked as a duplicate of this bug. ***
Comment 52 Oliver Brinzing 2019-03-29 22:02:54 UTC
*** Bug 124439 has been marked as a duplicate of this bug. ***
Comment 53 Buovjaga 2019-05-27 15:33:58 UTC
*** Bug 100914 has been marked as a duplicate of this bug. ***
Comment 54 Oliver Brinzing 2019-07-03 17:08:19 UTC
*** Bug 126212 has been marked as a duplicate of this bug. ***
Comment 55 kvoz123 2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.

Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary.  %-(
Comment 56 Luis Alberto Hernández Monroy 2019-11-23 04:31:03 UTC
Google Drive two-factor authentication not working on 6.3.3.2 I'm getting the "The specified device is invalid." when trying to setup the connection.
Comment 57 Aron Budea 2020-01-06 16:09:13 UTC
*** Bug 129835 has been marked as a duplicate of this bug. ***
Comment 58 Xisco Faulí 2020-01-20 18:47:05 UTC
*** Bug 127662 has been marked as a duplicate of this bug. ***