-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ownCloud 2.5: Config stored in %APPDATA%, but password is still stored in %LOCALAPPDATA% #6729
Comments
This probably can be fixed by building QtKeychain with |
Qt Keychain issue: frankosterfeld/qtkeychain#121 |
@jnweiger @michaelstingl If we want this in 2.5.0 it means we need a newer QtKeychain for Windows. |
How can we get "a newer QtKeychain for Windows"? |
We ask @frankosterfeld to make a new release/tag in his git repo (Sorry Frank..). (We can avoid this by just taking the sources directly from a fork). |
If it's not that much effort, @dschmidt could give it a try next week… |
The mingw toolchain should be in maintenance mode now. 2.5.0 development should be MSVC toolchain only. |
Otherwise the credentials are not preserved accross conneciton in a roaming setting Reported in owncloud/client#6729
@guruz 0.9.1 has been released |
FYI, according to @jakobvogel in atom/node-keytar#123 (Which is like QtKeyChain for nodejs) the CRED_PERSIST_ENTERPRISE will still read the old CRED_PERSIST_LOCAL_MACHINE too if it already existed 👍 |
Updated https://build.opensuse.org/package/show/isv:ownCloud:Qt5101/ocqt5101-qt5keychain |
@guruz ... a little caveat, though: While the old In order to upgrade legacy credentials to roam, it is probably necessary to delete the By the way, owncloud is a great piece of software. Love to use it myself. Thanks for your work! |
Latest MSI builds contain the new QtKeychain - please test |
Which builds do you mean? I have tested the following builds:
All of them still contain the old QtKeychain, where this bug is still present. Where can we get the latest MSI builds you are referring to? |
Yes, I just tested ownCloud-2.5.0.10597.-daily20180904.10541.msi and it is working properly - the password is now stored with "enterprise" scope, which means it'll be persisted in |
Thank you everyone... |
In ownCloud 2.5 the location of the config folder in Windows has changed from
%LOCALAPPDATA%
to%APPDATA%
, which is a good for roaming profiles (see #684) 👍 .This leads to a new issue though, because the password which is stored through QtKeychain is still stored in the local Windows credential store, which resides in
%LOCALAPPDATA%
.Expected behaviour
The password should be stored in the Windows Credential Manager with "enterprise persistence" instead of "local machine persistence". Otherwise the user has to enter the sync password on every machine on the network or - depending on the roaming profile policy - on each logon.
Actual behaviour
The user has to enter the sync password on every logon.
Steps to reproduce
This may also happen on the same machine, as "machine local" profiles are often not persisted after logging out.
Client configuration
Client version: 2.5.0 beta1
Operating system: Windows 7, Windows 10
The text was updated successfully, but these errors were encountered: