[Bug]: 3.15.x asks to log in on every start (PKCS#12 client certificate) #7762
Comments
|
@brdns sorry for the trouble |
|
@mgallien thanks for having a look at this ! Fortunately I’ve got a
And here’s a
Let me know if you need any further logs or feedback. |
|
same issue here |
|
Arch Linux and MacOS newest clients on both machines and latest stable v30 Nextcloud same problem. Every restart both Arch Linux and MacOS need re-authorization of the sync client. Re-installed both MacOS and Arch Linux and fresh install have this problem. |
Same here on EndeavourOS. Clicking on log-in to re-authenticate does nothing. I need to remove and re-add the account in the nextcloud desktop client including setting up every sync folder pairs on every reboot/user logout. Makes it basically unusable. |
I just gave up on Nextcloud. Tried it multiple times over the past 3 years, but you just can't use it. I switched to to owncloud OCIS for files, radicale for DAV, Immich for photos and hope this system works better in the long run. So far everything is great. |
|
@naifqarni @PhysicsIsAwesome Hello, can you also provide logs (preferably anonymized) ? So the Nextcloud devs can narrow down the issue, it might be different for you guys since you’re using different platforms. I’m also running a nextcloud client on a linux distro (Fedora) and so far that one is going smooth, I’m only having an issue with my Windows nextcloud client. Also is your bug related to the PKCS#12 client certificate login method specifically like in this issue ?
@mxsrm Hello, please keep comments on this issue strictly related to providing information that can help the devs fix it. I’ve used OCIS myself and it’s great software too but lacks the PKCS#12 client certificate login in their apps which I need. I’m glad the Nextcloud devs are working on it even though it still needs improvements. |
brdns
changed the title
Yes
Version 3.15.3daily, Erstellt aus der Git-Revision a595d5 auf Jan 7 2025, 13:56:30 unter Verwendung von Qt 6.8.1, OpenSSL 3.4.0 22 Oct 2024. Found the following warning level log entries multiple times: |
|
It has been quite some time since the desktop client has gone unusable for mTLS users. Anyone working on this? |
Bug description
Hello, I am also experiencing this issue with desktop client
3.15.3on 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: