You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am also experiencing this issue with desktop client 3.15.3 on Windows 11. There’s probably a link with the recent migration to Qt6 and the previous QtKeychain implementation in the client. That feature has not been updated since the first release so I’m tagging the most recent contributor to the file httpcredentials.cpp@mgallien and the original contributor @ckamm.
The initial connection works well while providing the PKCS#12 client certificate and the password. It seems there’s a mismatch where the certificate bundle is either not properly saved in the keychain or is not fetched correctly on the next login :
@brdns sorry for the trouble
can you check if the entry for password exists in the windows credentials manager ?
that would be nice to check and would help me narrow down the problem and find the best way to solve the issue
Fortunately I’ve got a 3.14.x client on another desktop which I have not yet updated. Here’s how the windows credentials manager look like on a working client that keeps the credentials even after reboot :
And here’s a 3.15.x client. The windows credentials manager only has one entry regarding Nextcloud, even before reboot while the client certificate is still somehow working :
Let me know if you need any further logs or feedback.
Bug description
Hello, I am also experiencing this issue with desktop client
3.15.3
on Windows 11. There’s probably a link with the recent migration to Qt6 and the previous QtKeychain implementation in the client. That feature has not been updated since the first release so I’m tagging the most recent contributor to the filehttpcredentials.cpp
@mgallien and the original contributor @ckamm.The initial connection works well while providing the PKCS#12 client certificate and the password. It seems there’s a mismatch where the certificate bundle is either not properly saved in the keychain or is not fetched correctly on the next login :
https://github.com/nextcloud/desktop/blob/master/src/libsync/creds/httpcredentials.cpp#L440
It seems the client certificate is found, but its password was not correctly saved and can’t be found on following attempts to login.
Steps to reproduce
Expected behavior
Client certificate file and password should be stored across client restarts and device reboots.
Which files are affected by this bug
httpcredentials.cpp
Operating system
Windows
Which version of the operating system you are running.
Windows 11 24h2
Package
Official Windows MSI
Nextcloud Server version
30.0.5
Nextcloud Desktop Client version
3.15.3
Is this bug present after an update or on a fresh install?
Fresh desktop client install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
Thank you so much for this great piece of software !!!
The text was updated successfully, but these errors were encountered: