Closed Bug 1054040 Opened 10 years ago Closed 6 years ago

Firefox OS (1.4) calendar cannot connect to Calendar Server (www.calendarserver.org)

Categories

(Firefox OS Graveyard :: Gaia::Calendar, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rlb, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.0 (Beta/Release)
Build ID: 20140803010241

Steps to reproduce:

I'm not very experienced with Calendar Server, so this migh be pilot error, but here's how you should be able to demonstrate the problem.

Install the Debian calendarserver package 5.2+dfsg-1 in a virtual machine (or wherever).  Change the permissions on the sudoers.plist, accounts.xml, and caldavd.plist files in /etc/caldavd to be group caldavd, 0640.

Follow the instructions in /usr/share/doc/calendarserver/README.Debian.gz, configuring the server for password based (non-peer) postgresql access.

Comment out the users in /etc/sudoers.list and add a single user, "rlb" (and password) to accounts.xml.  Enable a single https port, 8443, in caldavd.plist, and set AllowOverWireUnencrypted to false.

On any Firefox OS instance you intend to test, visit https://server:8443/calendars/users/rlb/calendar with the local browser, and accept the self-signed certificate.



Actual results:

An attempt to access https://server:8443/calendars/users/rlb/calendar from the Linux desktop Firefox browser, a Firefox OS 1.4 simulator browser, or a Flame browser, displays the calendar Collection Listing (after accepting the self-signed certificate and providing the username/password).

Attempting to configure that URL as a calendar in the calendar application on both the 1.4 simulator and on a Flame results in "Wrong login and/or password".

Examining /var/log/caldavd, I noticed that the browsers all appear to issue a GET, while the calendar application issues a PROPFIND.  Furthermore, if I issue the same PROPFIND via cadaver, I see that the attempt includes the username "rlb", and produces a 207 response, but the calendar application's attempt does not include the username, and produces a 401 (unauthorized) response.



Expected results:

The calendar application should have added the remote calendar.

Please let me know if I can provide any further testing/help.

Thanks
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.