Version: 4.3.4.1 Build ID: bc356b2f991740509f321d70e4512a6a54c5f243 Also on 4.4.0.0 beta1 Windows 8.1 I am trying to connect to a google account where the password includes several special characters in the password. The CMIS fails to return 'Google Drive' in the repository dropdown box which causes the failure of the connection to complete. Subsequently I created a 'fresh' gmail account where I set the password to a simple ascii only password and the connection works. There appears to be an issue with the escaping of the password when handling the authorisation. Kurt
Hey Kurt, Can you provide step by step instructions on how to do this? It's always best for the reporter of a bug to provide step by step instructions because it's impossible for us to know everything that LibreOffice is capable of and is almost always faster for a user to explain the use case, give explicit instructions, and then we'll try to reproduce. Please include an example password that we can try for our google drive account Setting to NEEDINFO - once you provide clear steps please set the bug to UNCONFIRMED. Thanks!
With Libreoffice set to "Use LibreOffice dialogue boxes" checked (Tools->Options->LibreOffice->General) 1. Open new Writer document 2. Save As 3. Clicker "Server..." button 4. Give server name `server name` 5. Select "CMIS" file service type 6. Server details "Google Drive" 7. Press refresh button next to Repository dropdown box 8. Fill in username and password (need to employ a password such as `&password` specifically with ampersand) 9. Nothing happens What should happen If the gmail account has a password without ampersand then the connection is made and the repository "Google Drive" appears in the dropdown list enabling the OK button to be clicked. Hope that is enough to replicate the problem. Thanks, Kurt
just setting to unconfirmed after updated steps.
(In reply to kurt forrester from comment #2) > With Libreoffice set to "Use LibreOffice dialogue boxes" checked > (Tools->Options->LibreOffice->General) > > 1. Open new Writer document > 2. Save As > 3. Clicker "Server..." button > 4. Give server name `server name` > 5. Select "CMIS" file service type > 6. Server details "Google Drive" I'm not seeing this step. When I select CMIS and then do the dropdown next to "Server Type" I see the following: Alfresco 4 IBM FileNet P8 Lotus Live Files Nuxeo 5.4 OpenDataSpace OpenText ELS 10.2.0 SharePoint 2010 Are you using an extension?
I am using the vanilla version 4.3.4.1 from the Document Foundation website (http://donate.libreoffice.org/home/dl/win-x86/4.3.4/en-GB/LibreOffice_4.3.4_Win_x86.msi). This is a new feature within the CMIS system so unless you are running the same version then I think you will not see the functionality that I and reporting against. Can you confirm you are using Windows and the version noted in the bug report? Kurt
Windows 7 LibreOffice 4.3.4.1 release Confirmed: Setting to: New
Adding Cedric as he was involved with implementation of Google Drive stuff.
Bump
Please don't "bump" bugs - it literally does nothing other than annoy developers and clog the bug tracker. Thanks
Just to mention that I really have no time to work on it these days... will thus suffer from delay in fixing it.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Dear kurt forrester, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
There have been several fixes to G. Drive support over the years. Bug 101630 just got a fixing commit, could you please re-test with Win-x86_64@tb77-TDF https://dev-builds.libreoffice.org/daily/master/current.html after it has a build from 2021-07-28 or later?
Cloph tells me the authentication now happens in the browser with the server directly, LibreOffice only gets the return code, so this is obsolete.