[Akonadi] [Bug 319227] New: access denied to owncloud caldav/carddav after it's been synched with a syncevolution client

[list-ener at strank.info]

https://bugs.kde.org/show_bug.cgi?id=319227

            Bug ID: 319227
           Summary: access denied to owncloud caldav/carddav after it's
                    been synched with a syncevolution client
    Classification: Unclassified
           Product: Akonadi
           Version: 1.9.1
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: DAV Resource
          Assignee: kdepim-bugs at kde.org
          Reporter: list-ener at strank.info

I have an owncloud server (v.5.0.5 both calendar and contacts), kde akonadi
(1.9.1 on kubuntu), a Nokia N9 running syncevolution (1.3+20120925).

Using the N9 with the owncloud server: no problem

Using kde akonadi with the owncloud server: no problem

But since the update of owncloud to 5.0.5 the following happens:
once I use the N9 syncevolution client to sync (even if there are no changes to
sync), the kde akonadi client fails with an "access denied" message for each
calendar and contacts group (obviously the password didn't change). Using
exactly those same URLs from the error messages in a browser shows the correct
data after entering the password. Editing the akonadi resource settings (e.g.
deleting the password, and later entering it again) has no effect.

Deleting the resource and re-creating it with the exact same settings leads to
a working sync-agent again... until the next sync of the other client.

My guess is that the akonadi client caches something that gets invalidated by
the other client, which is why I report that bug here.

Where do I find/enable detailed logs from the akonadi agent to get to the
bottom of this?

Reproducible: Always

Steps to Reproduce:
1. Setup akonadi owncloud client
2. Sync another client (syncevolution) with the server
3. Next sync of the akonadi client
Actual Results:  
Akonadi client fails with "access denied"

Expected Results:  
Acess granted as before

-- 
You are receiving this mail because:
You are the assignee for the bug.