Description: Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: CL I want to access and edit my Google Drive documents. I tried to add Google Drive to the service. I enter my user name/password (correct because from my password manager) and then I get prompted for a 6-digit PIN. I check my phone and nothing was sent. My PIN works with Google services and when Google determines it is needed, I correctly get a text message from Google. Reading through comments from a Google search on this problem, LibreOffice has NOT posted a solution to this problem in a long time. Why? The problem is heavily documented in Google search. Steps to Reproduce: 1. Have a Google account with Google drive active. 2. Have correctly setup your mobile phone number with Google 3. Have successfully received Google two-factor authentication using text message to your phone. 4. Open LibreOffice on your Linux computer. 5. Try to add the Google Drive service 6. Enter your Google username/password at the prompt 7. Receive the prompt to enter the non-existent 6 digit PIN Actual Results: No PIN received by phone or email. Unable to proceed further. Expected Results: LibreOffice should be accepting the valid username/password and not prompting for a PIN. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: CL
Perhaps it's not been fixed because: - LO devs don't use it - Google had changed the way to authenticate several times - there are a lot of bugs declared and this one is not a priority Anyway, feel free to contribute (see https://wiki.documentfoundation.org/Development/GetInvolved) or if you're not a dev, you may also pay someone to contribute.
Seems to be a duplicate bug tdf#101630 *Google Drive two-factor authentication (2FA) not working again*
*** This bug has been marked as a duplicate of bug 101630 ***