Closed
Bug 1255047
Opened 10 years ago
Closed 9 years ago
Password Manager does not store Lightning CalDAV login (TB 38.6.0)
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: thindraug, Unassigned)
Details
(Keywords: calendar-integration)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20160210153822
Steps to reproduce:
I upgraded TB from 38.4 to 38.6 (with calendar.network.multi realm set to TRUE).
No changes in the OwnCloud CalDAV server (8.2.2.2) before/after the TB update.
My calendars are accessible in the form:
https://[server]/remote.php/caldav/calendars/[user]/[calendar1|calendar2|calendar3]
Actual results:
On TB start after updating, password manager stopped saving the CalDAV passwords and re-prompted me in an endless loop.
I removed all three calendars and added them again. They were correctly imported (so, user/pass works), but after their sync interval (30min) has passed, the credential pop-ups came back.
On some occasions, 1 calendar keeps working, on others, I am prompted for 3 passwords.
Error console shows:
Error: [calCachedCalendar] replay action failed: null, uri=https://[server]/remote.php/caldav/calendars/[user]/[cal_x], result=2147500037, op=[xpconnect wrapped calIOperation]
Source: file:///[...]/AppData/Roaming/Thunderbird/Profiles/[profile]/extensions/[hash]/calendar-js/calCachedCalendar.js, Line: 322
Expected results:
Calendars should have stayed accessible and passwords correctly stored in/retrieved from Password Manager.
I am aware that there have been similar bugs in the past, but so far, none of the ideas thrown around on older forum threads (switching multirealm setting, checking SSL certificate validity, etc.) did fix this.
Upgrading from TB 38.6 to 38.7.0 did fix the problem.
Currently upgrading from 38.7 to 45.1.0, will post back if that changes things again.
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•