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

Jasper Olbrich jasper.olbrich at students.uni-marburg.de
Thu Aug 21 14:41:25 UTC 2014



On 21.08.2014 16:25, Stephan Kleber wrote:
> Hi,
>
> 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:

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.

HTH,
Jasper


More information about the horde mailing list