Bug 509837 - Akonadi/DAV groupware ressource doesn't report failed logins to user
Summary: Akonadi/DAV groupware ressource doesn't report failed logins to user
Status: REPORTED
Alias: None
Product: kdepim
Classification: Applications
Component: general (other bugs)
Version First Reported In: 6.5.2
Platform: NixOS Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-23 17:25 UTC by Thomas Baag
Modified: 2025-09-23 17:25 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Baag 2025-09-23 17:25:16 UTC 
SUMMARY

Hi, if the akonadi_davgroupware_resource is unable to login to e.g. Nextcloud it seems to have no way to report this issue to the user. In the case of using Nextcloud this results in getting banned by the brute-force detection.

STEPS TO REPRODUCE
1. Configure DAV with Nextcloud calendar.
2. Change user password in Nextcloud or for the DAV ressource.

OBSERVED RESULT
Getting your IP address throttled in Nextcloud. DAV agent state in Akonadi is marked as "Ready" and "Online". It looks as happy as it can be in Akonadi Console.

EXPECTED RESULT
Getting a dialog displayed informing me about failed login issues and maybe asking for updated credentials. A failure state of the DAV agent in Akonadi is expected as well.

ADDITIONAL INFORMATION
Logs only show a vague HTTP error "0".
org.kde.pim.davresource: Unable to fetch collections 300 "There was a problem with the request.\nHTTP error (0)."
It does display the correct HTTP error "429" when throttled.
org.kde.pim.davresource: Unable to fetch collections 300 "There was a problem with the request.\nHTTP error (429)."

I tested a generic PROPFIND with cURL to the same Nextcloud which gave me a "HTTP/2 401" when using wrong credentials. So it looks to me like the problem is NOT with Nextcloud giving HTTP 0 as a return code.