SUMMARY I've previously added a webdavs remote directory targeting Nextcloud in Dolphin on Kubuntu 20.4.3 using an URI such as webdavs://user@local.domain:443/remote.php/dav/files/user/. Since then I've changed my password on Nextcloud, now Dolphin obviously fails to connect but does not ask for credentials again. The credentials are not available in the KDE wallet manager. As Dolphin repeatedly attempts to authenticate with the deprecated credentials, the user account will potentially be disabled. STEPS TO REPRODUCE 1. Add remote webdavs location (such as Nextcloud, e.g. "webdavs://user@local.domain:443/remote.php/dav/files/user/") 2. Enter credentials and access resource 3. Change credentials on webdavs authentication platform 4. Connect to webdavs resource via Dolphin again 5. Dolphin now attempts to authenticate with the cached credentials and won't ask for new credentials or allow clearing the stored username and password. OBSERVED RESULT Authentication will fail and I am unable to identify a process to clear/delete cached credentials. EXPECTED RESULT Once the authentication fails, it should be possible to enter new credentials and an option to remove credentials should be available. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.4.3 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION My online research repeatedly mentions KDE Wallet Manager, with the option to delete cached credentials there. However, the KDE Wallet Manager does not hold any related data for me.
Closing Dolphin, Updating Kubuntu and a reboot later, Dolphin now asks for the credentials again. I still have no idea where those were cached and how I could have re-entered new credentials.
Same issue here, no idea where the credential are stored. Another thing to add, accessing a webdav on the same server with a different username don't work. Dolpin uses the same cached username. No way of removing or editing cached credential. Please help!
Exactly the same thing here, I'd rather not have to log out and back in, then open everything back up just to clear cached credentials. Nothing in KDE wallet, nothing obvious in any cache/config directories (which makes sense if its in memory). I discovered that killing `kiod5` and `kioslave5` processes was able to clear the state and prompt for credentials again. Probably not the best thing to do, but so far I haven't noticed any adverse effects as the processes do restart when connecting