6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
8/20/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#13449] CalDAV / CardDAV sync need multiple logins / session to work
*
Your Email Address
*
Spam protection
Enter the letters below:
.___..___.___.\ /.__. _/ [__ _/ >< | | ./__.| ./__./ \|__\
Comment
>> Regarding the Thunderbird/Lightning issue: >> >> I think this bug https://bugzilla.mozilla.org/show_bug.cgi?id=799184#c15 >> describes it perfectly. It seems to be a known problem with the password >> manager. Definitely not a bug in Horde. > > Hi all, > > I don't think that the behavior described for TB (31.2.0) and Horde > is caused by the above TB bug. I have the same problem described > already in the ticket since I updated Horde to 5.2.3. Before the > update I can access two Horde calendars and two Horde addressbooks > (SoGo connector) from TB. The passwords had been stored with the > password manager in TB (mutliream=true). > > After the update of Horde, TB randomly askes for the passwords > (sometimes for just one calendar, sometimes for a calendar and a > addressbook, etc.), even they are stored in the TB password manager. > Before the password dialog opens in TB, there is already the log > entriy as described in the ticket before. The log with DEBUG enabled: > > Nov 20 21:00:43 HORDE: [imp] [login] No password provided. [pid 2934 > on line 730 of "/usr/share/horde/imp/lib/Imap.php"] > Nov 20 21:00:43 HORDE: 1. require() > /usr/share/horde/rpc/index.php:14#012 2. > Horde_Rpc_Webdav->getResponse() /usr/share/horde/rpc.php:159#012 3. > Sabre\DAV\Server->exec() /usr/share/php/Horde/Rpc/Webdav.php:67#012 > 4. Sabre\DAV\Server->invokeMethod() > /usr/share/php/Sabre/DAV/Server.php:214#012 5. > Sabre\DAV\Server->broadcastEvent() > /usr/share/php/Sabre/DAV/Server.php:455#012 6. call_user_func_array() > /usr/share/php/Sabre/DAV/Server.php:433#012 7. > Sabre\DAV\Auth\Plugin->beforeMethod()#012 8. > Sabre\DAV\Auth\Backend\AbstractBasic->authenticate() > /usr/share/php/Sabre/DAV/Auth/Plugin.php:108#012 9. > Horde_Dav_Auth->validateUserPass() > /usr/share/php/Sabre/DAV/Auth/Backend/AbstractBasic.php:77#01210. > Horde_Core_Auth_Application->authenticate() > /usr/share/php/Horde/Dav/Auth.php:54#01211. > Horde_Core_Auth_Application->authenticate() > /usr/share/php/Horde/Core/Auth/Application.php:126#01212. > Horde_Auth_Base->authenticate() > /usr/share/php/Horde/Core/Auth/Application.php:129#01213. > Horde_Core_Auth_Application->_authenticate() > /usr/share/php/Horde/Auth/Base.php:160#01214. > Horde_Registry->callAppMethod() > /usr/share/php/Horde/Core/Auth/Application.php:158#01215. > call_user_func_array() /usr/share/php/Horde/Registry.php:1201#01216. > IMP_Application->authAuthenticate()#01217. IMP_Auth::authenticate() > /usr/share/horde/imp/lib/Application.php:371#01218. IMP_Imap->login() > /usr/share/horde/imp/lib/Auth.php:86#01219. IMP_Imap->__call() > /usr/share/horde/imp/lib/Auth.php:86#01220. require() > /usr/share/horde/rpc/index.php:14#01221. > Horde_Rpc_Webdav->getResponse() /usr/share/horde/rpc.php:159#01222. > Sabre\DAV\Server->exec() > /usr/share/php/Horde/Rpc/Webdav.php:67#01223. > Sabre\DAV\Server->invokeMethod() > /usr/share/php/Sabre/DAV/Server.php:214#01224. > Sabre\DAV\Server->broadcastEvent() > /usr/share/php/Sabre/DAV/Server.php:455#01225. call_user_func_array() > /usr/share/php/Sabre/DAV/Server.php:433#01226. > Sabre\DAV\Auth\Plugin->beforeMethod()#01227. > Sabre\DAV\Auth\Backend\AbstractBasic->authenticate() > /usr/share/php/Sabre/DAV/Auth/Plugin.php:108#01228. > Horde_Dav_Auth->validateUserPass() > /usr/share/php/Sabre/DAV/Auth/Backend/AbstractBasic.php:77#01229. > Horde_Core_Auth_Application->authenticate() > /usr/share/php/Horde/Dav/Auth.php:54#01230. > Horde_Core_Auth_Application->authenticate() > /usr/share/php/Horde/Core/Auth/Application.php:126#01231. > Horde_Auth_Base->authenticate() > /usr/share/php/Horde/Core/Auth/Application.php:129#01232. > Horde_Core_Auth_Application->_authenticate() > /usr/share/php/Horde/Auth/Base.php:160#01233. > Horde_Registry->callAppMethod() > /usr/share/php/Horde/Core/Auth/Application.php:158#01234. > call_user_func_array() /usr/share/php/Horde/Registry.php:1201#01235. > IMP_Application->authAuthenticate()#01236. IMP_Auth::authenticate() > /usr/share/horde/imp/lib/Application.php:371#01237. IMP_Imap->login() > /usr/share/horde/imp/lib/Auth.php:86#01238. IMP_Imap->__call() > /usr/share/horde/imp/lib/Auth.php:86#01239. call_user_func_array() > /usr/share/horde/imp/lib/Imap.php:718#01240. > Horde_Imap_Client_Base->login()#01241. > Horde_Imap_Client_Socket->_login() > /usr/share/php/Horde/Imap/Client/Base.php:794 > Nov 20 21:00:43 HORDE: [imp] FAILED LOGIN for XXXX (192.168.8.254) > to {imap://192.168.6.231/} [pid 2934 on line 157 of > "/usr/share/horde/imp/lib/Auth.php"] > > Can I do more debugging to see what user and password is given to > Horde? Can I do anything else to help find the bug? > > Kind regards > Torsten >
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers