[Tickets #13449] CalDAV / CardDAV sync need multiple logins / session to work
noreply at bugs.horde.org
noreply at bugs.horde.org
Mon Aug 18 13:14:07 UTC 2014
BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE
E-MAIL-ADRESSE WERDEN NICHT GELESEN.
Ticket-URL: http://bugs.horde.org/ticket/13449
------------------------------------------------------------------------------
Ticket | 13449
Erstellt Von | hn at axxedia-it.de
Zusammenfassung | CalDAV / CardDAV sync need multiple logins / session to
| work
Warteschlange | Horde Groupware Webmail Edition
Version | 5.2.1
Typ | Bug
Status | Unconfirmed
Priorität | 2. Medium
Milestone |
Patch |
Zuständige |
------------------------------------------------------------------------------
hn at axxedia-it.de (2014-08-18 13:14) hat geschrieben:
I have a customer using Horde with iCAL4OL to sync calendars and
contacts between users. After upgrading to 5.2.1 from 5.1.6 they
cannot use iCAL4OL anymore, because there seems to be a problem with
the authentication. iCAL4OL starts a CalDAV sync with the given
credentials, then it gets disconnected and cannot authenticate again,
because it tries to use the previous session which is not available
any longer.
I did have a quick check with the developer of iCAL4OL who found out,
that if iCAL4OL sends the login credentials each time the server asks
for them (new connection / new ssl-handshake) it works fine. This
behavior can also be seen on the demo server you provide, so it is not
a configuration problem on my customers server.
In the syslog a failed connection attempt then looks like this:
HORDE: [imp] Login success for tb (zensiert) to {imap://localhost/}
[pid 9310 on line 157 of "/var/www/webmail/imp/lib/Auth.p$
Aug 18 11:21:31 khs-server HORDE: [imp] [login] No password provided.
[pid 9310 on line 732 of "/var/www/webmail/imp/lib/Imap.php"]
Aug 18 11:21:31 khs-server HORDE: [imp] [login] No password provided.
[pid 9855 on line 732 of "/var/www/webmail/imp/lib/Imap.php"]
In 5.1.6 it was possible to reuse the existing connection thus it was
not necessary to send the login credentials each time. We suspect a
configuration error somewhere in the SabreDAV settings in Horde.
I also did a quick check with CalDAV Sync for android, and it looks
like this app does handle the login problem by itself, because I can
see it doing multiple logins / new connections during one
synchronisation attempt.
More information about the bugs
mailing list