even a correct login causes a login loop on a caldav calendar

UNCONFIRMED
Unassigned

Status

UNCONFIRMED
6 years ago
7 months ago

People

(Reporter: vonkaenel, Unassigned)

Tracking

Lightning 1.9

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Created attachment 686111 [details]
login.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0
Build ID: 20121119183901

Steps to reproduce:

We have calendars on a communigate pro server v 5.4.8
We can access them with lightning 1.9 in the form of:
https://<mail server>/CalDAV/Calendar



Actual results:

After entering the username and password the login window reappears. Now I have to cancel the login window without entering anything and all works fine.

Even when I store the username and password in thunderbird the login screen appears during startup of thunderbird. Also here cancel the login window helps.

Thunderbird errors:
Warnung: getAttributeNodeNS() sollte nicht mehr verwendet werden. Verwenden Sie stattdessen getAttributeNS().
Quelldatei: resource://calendar/modules/calXMLUtils.jsm

Warnung: Das ownerDocument-Attribut auf Attributen sollte nicht mehr verwendet werden.
Quelldatei: resource://calendar/modules/calXMLUtils.jsm


Expected results:

The reappearance of the login window is confusing. You always thinks you gave the wrong password.
(Reporter)

Updated

6 years ago
Component: General → Provider: CalDAV
Could you enable calendar.debug.log and calendar.debug.log.verbose in the advanced config editor (Options > Advanced > General > Config Editor) and show us some logs about what is happening when you do this?
Flags: needinfo?(vonkaenel)
(Reporter)

Comment 2

4 years ago
Hi Philipp

Thank you for your hint.
The problem has to do with CalDAV: send: PROFIND ...
One user works an other not. It could be because communigate pro cannot work with the default calendar (ommited in the CalDAV link). I am going to investigate and tell you later.

Stefan
Flags: needinfo?(vonkaenel)
You need to log in before you can comment on or make changes to this bug.