Linux 5.0.2.2 de Win 5.0.3.2 de Win 5.0.4.x de the check in "Password need" writes in Contend.xml "<db:login db:user-name="anyone" db:is-password-required="true"/> but the uncheck dos not work. there is no change in Contend.xml Only edit Contend.xml solve this problem.
Edit / Database / Properties is greyed out for me. How can I activate it?
(In reply to Beluga from comment #1) > Edit / Database / Properties is greyed out for me. How can I activate it? When you use a database HSQLDB you don't need this. When using a postgreSQL DB it is aktive and not greyed out. There are two ways to logon: The same user as the Linux User is defined in the DB, there is not a password required. If you want to connect with an other user, then a password is needed.
Could not confirm this bug. Have tested this: Opened a database, which needs a password (MySQL - direct connection). Unchecked in Edit > Database > Properties "Password need". Closed the *.odb-file and opened again. When trying to connect to the database (changing to the table-container) it throws an error: Access denied ... (using password: NO) ... but I would never use a Server-database without a different password as required for a normal user on my system ... My system: OpenSUSE 42.1 64bit rpm Linux, LO 5.0.5.1. Version in this bug is wrong. I have set it to the first version the bug is reported for ...
(In reply to robert from comment #3) > ... but I would never use a Server-database without a different password as > required for a normal user on my system ... In PostgreSQL, an option is that a local user can connect to a database as the same user without any password; the (e)uid of the calling process is checked and this is trusted.
Changed title to reflect bug description
Confirming with LO 5132 on OSX 10.11.5 How to reproduce : 1) Create an ODB file that connects to an existing posgres db. 2) Enter a username/password for connecting to the db - test the connection. 3) Complete the wizard and save the odb file. 4) In the tables mode of the ODB container window, right mouse button click in the lower window and choose Database > Properties 5) Untick the password box. 6) Save the ODB file, close it and quit LO. 7) Now inspect the ODB file by unzipping it (changing extension from odb to zip as necessary dependent on your OS and any built in archive tools). Look at the file content.xml. It contains the following : xlink:href="sdbc:postgresql:postgresql://localhost/alex" xlink:type="simple"/><db:login db:user-name="alex" db:is-password-required="true"/></db:connection-data><db:driver-settings Confirming.
Is this specific to Postresql connections or does it happen also with ODBC or JDBC or any other connection type where "needs password" is not greyed out?
Same thing happens with my jdbc connection between Base (Version: 5.1.4.2 Build ID: 1:5.1.4-0ubuntu1) and database Firebird 3.0 on Linux Mint 18. This does not have anything to do with Firebird, as shown by the workaround. Workaround: Know that the *.odb-file is really a *.zip-Archive that contains all the settings. Open and edit it: 1. Rightclick on *.odb - file 2. Open With File-Roller (German: Archivverwaltung) or any application that opens *.zip files; you should see a datastructure now with folder "Configurations2, folder "forms"... until file "settings.xml". In the middle you see file "content.xml". 3. Open file "content.xml" with any simple text editor (in my case: xed). 4. Search for db:is-password-required. 5. You'll find: db:is-password-required="true". 6. Change this to db:is-password-required="false". 7. Save and close file "content.xml". 8. Close file-roller or whatever you unpacked the *odb-file. That's it. Now you can open your database without entering a password and, if you want to check, the field "Password required" in the configuration window Connection settings (Get there by: Menu | Edit | Database | Properties) is unchecked.
Suggestion of a fix: My workaround in comment 8 (Wolfgang 2016-07-31 20:47:23 UTC) suggests strongly that the bug's reason is that unchecking the the Menu | Edit | Database | Properties | "Password required" checkbox does not set entry in file content.xml in zip-archive/file *.odb) from 'db:is-password-required="true"' to 'db:is-password-required="false"'. However (I just tested it): Checking the "Password required" checkbox *does* set the above mentioned entry to 'db:is-password-required="true"'! Thus, the bug is between the user interface and the underlying *.odb file; that should not be too hard to fix (repair one line?). Good luck! And thank you to whomever does this.
** 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.4.1 or 5.3.6 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-20170901
Bug not surprisingly still present in Version: 5.4.0.3 Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: group
This bug is still present in Beta of: Version: 6.0.0.1 Build ID: d2bec56d7865f05a1003dc88449f2b0fdd85309a CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group Please note: This also involves those using 'split' databases where an errant setting cannot be cleared without editing the 'content.xml' file.
bug still present Version: 6.0.4.2 (x64) Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf Windows 10
Dear Heinz-Dieter, 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
On pc Debian x86-64 with master sources updated today + postgres native, I could reproduce this. I submitted a patch here: https://gerrit.libreoffice.org/c/core/+/94363
Julien Nabet committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/71c8f9cf3825b53efc8841fa3bc9144e90bc189a tdf#97416: fix Database password properties in ODB file not re-settable via UI It will be available in 7.0.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Patch waiting for review for 6.4 branch: https://gerrit.libreoffice.org/c/core/+/94374
Julien Nabet committed a patch related to this issue. It has been pushed to "libreoffice-6-4": https://git.libreoffice.org/core/commit/10444727db12d371e99c4ce4bdb74cf9ca8b87b8 tdf#97416: fix Database password properties in ODB file not re-settable via UI It will be available in 6.4.5. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.