Bug 319227 - access denied to owncloud caldav/carddav after it's been synched with a syncevolution client
Summary: access denied to owncloud caldav/carddav after it's been synched with a synce...
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: DAV Resource (show other bugs)
Version: 1.9.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-02 15:00 UTC by list-ener
Modified: 2014-09-30 18:45 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description list-ener 2013-05-02 15:00:09 UTC
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
Comment 1 eArquilla 2013-05-10 16:45:04 UTC
i have same issue. owncloud 5.05 , gentoo running kde4.10.3
Comment 2 Olivier M. 2013-05-22 06:43:44 UTC
As useless as it is, same problem here since yesterday. I'm using Owncloud 5.0.5 (updated to 5.0.6 once it started failing, to no avail). My desktop uses KUbuntu 13.04 (Akonadi 1.9.1), and keeps giving me "access denied" and "impossible to create the collection" on every sync.

The only other sync-source I have is an Android-phone with CardDAV-Sync and CalDAV-Sync (both paid versions). The whole thing worked like a charm for weeks.

My HTTP server's logs doesn't show anything upon failures. My Owncloud's logs are full of this, though I'm not sure it's related to our problem : 

{"app":"core","message":"Adding user backend instance of OC_User_Database.","level":0,"time":1369204934}
{"app":"core","message":"Adding user backend instance of OC_User_Database.","level":0,"time":1369204959}
{"app":"core","message":"Adding user backend instance of OCA\\user_ldap\\USER_LDAP.","level":0,"time":1369204959}
{"app":"core","message":"Adding user backend instance of OC_User_Database.","level":0,"time":1369204959}
{"app":"core","message":"Adding user backend instance of OCA\\user_ldap\\USER_LDAP.","level":0,"time":1369204959}
{"app":"core","message":"include path for class \"OC_Connector_Sabre_CalDAV\" starts with \"apps\/\"","level":0,"time":1369204959}
{"app":"core","message":"include path for class \"OC_Connector_Sabre_CalDAV_CalendarRoot\" starts with \"apps\/\"","level":0,"time":1369204959}
{"app":"core","message":"Adding user backend instance of OC_User_Database.","level":0,"time":1369204959}
{"app":"core","message":"Adding user backend instance of OCA\\user_ldap\\USER_LDAP.","level":0,"time":1369204959}
{"app":"core","message":"include path for class \"OC_Connector_Sabre_CalDAV\" starts with \"apps\/\"","level":0,"time":1369204959}
{"app":"core","message":"include path for class \"OC_Connector_Sabre_CalDAV_CalendarRoot\" starts with \"apps\/\"","level":0,"time":1369204959}
{"app":"core","message":"Adding user backend instance of OC_User_Database.","level":0,"time":1369204960}
{"app":"core","message":"Adding user backend instance of OCA\\user_ldap\\USER_LDAP.","level":0,"time":1369204960}
{"app":"core","message":"include path for class \"OC_Connector_Sabre_CalDAV\" starts with \"apps\/\"","level":0,"time":1369204960}
{"app":"core","message":"include path for class \"OC_Connector_Sabre_CalDAV_CalendarRoot\" starts with \"apps\/\"","level":0,"time":1369204960}
{"app":"core","message":"Adding user backend instance of OC_User_Database.","level":0,"time":1369204962}
{"app":"core","message":"Adding user backend instance of OC_User_Database.","level":0,"time":1369204962}
{"app":"core","message":"Adding user backend instance of OCA\\user_ldap\\USER_LDAP.","level":0,"time":1369204962}
{"app":"core","message":"Adding user backend instance of OC_User_Database.","level":0,"time":1369204963}
{"app":"core","message":"Adding user backend instance of OCA\\user_ldap\\USER_LDAP.","level":0,"time":1369204963}
{"app":"PHP","message":"ldap_start_tls(): Unable to start TLS: Protocol error at \/var\/www\/owncloud-faitch\/apps\/user_ldap\/lib\/connection.php#616","level":2,"time":1369204963}
{"app":"PHP","message":"ldap_start_tls(): Unable to start TLS: Protocol error at \/var\/www\/owncloud-faitch\/apps\/user_ldap\/lib\/connection.php#616","level":2,"time":1369204963}
{"app":"core","message":"Adding user backend instance of OC_User_Database.","level":0,"time":1369204964}
Comment 3 Grégory Oestreicher 2014-09-05 20:43:46 UTC
Is this bug still present in the latest release?
Comment 4 Olivier M. 2014-09-11 14:27:46 UTC
As far as I can tell, everything fine here (Akonadi Server 1.12.1-0ubuntu1, and Owncloud 7.0.2).
Comment 5 Grégory Oestreicher 2014-09-30 18:45:38 UTC
Marking as fixed then, feel free to reopen if needed.

Thanks,
Grégory