[horde] Authenticated CalDAV import broken in Turba since Version 4.2

[Stephan Kleber]

Am 21.08.2014 16:41, schrieb Jasper Olbrich:
>> I have some external calendars imported via CalDAV into Horde (de:
>> "Externe Kalender"). So this is the other way around than the
>> problematic SabreDAV export of Horde-Calendars.
>>
>> It worked flawlessly to import, for example SOGo-Calendars, with
>> authentication on the SOGo-end into the Turba frontend.
>>
>> Since update to Version 4.2 of Turba the same calendars always issue a
>> notification saying the credentials are wrong (de: "Die Anmeldedaten,
>> die Sie angegeben haben, wurden nicht akzeptiert."). There are no
>> further relevant log entries even for raising the log level to extremes
>> (in horde and/or php). Import of unauthenticated (public) CalDAV sources
>> does work, however.
>>
>> Deleting the calendars and trying to add them back results in the same
>> notification. The external credentials have not changed and definitely
>> are right. CalDAV in SOGo works great for e.g. Thunderbird and did
>> before Version 4.2 in Turba.
> 
> Hello,
> 
> do you mean Kronolith instead of Turba? This issue is already bug tracked:
Of course I meant Kronolith! Thanks for setting me right.

> http://bugs.horde.org/ticket/13372
> 
> There's a "quick and dirty" fix in this bug ticket that works well for
> us. In the "duplicate" ticket, there is a somewhat more elaborate fix
> that tries to store the auth method for newly created calendars.

I tried both patches:
The elaborate fix for "duplicate" ticket 13319 does not work for me. The
effect has not changed, just applying this.

The "quick and dirty" fix mentioned in ticket 13372 solves the problem
for now.

Thanks very much for pointing the right direction.

Stephan



-- 
Stephan Kleber, M. Sc.
stephan at skleber.de