Bug 425086 - Webdav setup caches bad credential and uses it until I logout/login aka only prompts for credential ONCE
Summary: Webdav setup caches bad credential and uses it until I logout/login aka only ...
Status: CONFIRMED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: WebDAV (show other bugs)
Version: 5.54.0
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-06 21:24 UTC by Lad
Modified: 2024-11-04 20:05 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lad 2020-08-06 21:24:25 UTC
SUMMARY

When I setup a setup a webdav network drive
Dolphin prompts for credential
I mistype aka "typo" my password and submit the form
Dolphin attempts to connect and fails to connect
I try to submit the form again (thinking it will ask my password again)
Dolphin does not prompt for password again, but fails the connect


STEPS TO REPRODUCE
1. Set up a webdav network drive
2. Enter correct user/server/folder 
3. Enter incorrect password when prompted for password

OBSERVED RESULT

Dolphin seems to cache the mistyped credential and uses it for subsequent connection requests

EXPECTED RESULT

Dolphin should prompt for the credential again

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Debian 10
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
Comment 1 GfEw 2024-11-03 00:07:35 UTC
I can confirm this bug still persists with

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: MX 23 KDE
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

I also want to add: 

The only way I know to get back to normal so you're prompted for the WEBDAV password again is
1. completely log out of your KDE session
2. login to KDE again
3. initiate a connection to the WEBDAV share again.
If you need to quickly check sth on a particular share and happen to mistype the password, the sudden, unexpected requirement to terminate your entire KDE session in order to just successfully connect to that share, can be really disturbing.