Simple to fix the SSL issues. Create your own root certificate which you install on your clients.
Then create a cert for your calendar server and sign it with your new root certificate. Check my website http://www.rho.cc for a step by step guide. It's for Asterisk PBX but the steps are the same. ---Guy (via iPhone) On 9 Apr 2010, at 19:16, John Murdie <j...@cs.york.ac.uk> wrote: > I've been experimenting with Calendar Server 2.4 on (Slackware) Linux > (13.0), and would like to compare notes. I'm using only SSL and have > provided a self-signed certificate - I'd need to stump up some money for > something better. I'm using accounts.xml just to experiment with. > > Evolution 2.62.2 seems fine as "user01" (or anyone else), but with > Sunbird 1.0b1 (though Sunbird is obsolescent) and also in Thunderbird > 3.0.4 with Lightning 1.0b1, I've fallen foul of Bug 523555 - "Cannot add > CalDAV calendar via HTTPS if server has invalid/self-signed certificate" > - https://bugzilla.mozilla.org/show_bug.cgi?id=523555 - fixed in > development code on the 27th March, apparently. > > I had iCal 4.0.2 working fine on Mac OS X 10.6 without SSL with Calendar > Server 2.3, but now with 2.4 when I try: iCal -> Preferences -> Accounts > and click "+", and following http://support.apple.com/kb/HT3861 for > rough guidance, I see: > > Page "Add an account" > - - - - - - - - - - - > > Account type: CalDAV > User name: user01 > Password: user01 > Server address: https://calendar.mydomain.tld:8443/calendars/users/user01 > > Create. > > Verifying ... "No CalDAV server was found at the specified address." > > Continue. > > Page "Calendar Server Options" > - - - - - - - - - - - - - - - > > Account Template: iCal Server > User name: user01 > Password: user01 > Server address: https://calendar.cs.york.ac.uk > Server path: /calendars/users/user01/ > Port: 8443 Use SSL: yes > > Create. "The account information was not found. Async operation timed > out". > > Nothing visible in calendar server error log while this is going on, > debug level = "info". > > Next step is Kerberos, once I find a fix or a work-around for the above > problems. > > John A. Murdie > > _______________________________________________ > calendarserver-users mailing list > calendarserver-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
