CalDAV with Leopard iCal: Difference between revisions

m (Typo)
No edit summary
 
(23 intermediate revisions by 6 users not shown)
Line 1: Line 1:
=Introduction=
{{Archive}}=Introduction=
Zimbra 5.0 Supports the CalDAV standard. CalDAV is a protocol allowing calendar access via WebDAV. CalDAV models calendar events as HTTP resources in iCal format, and models calendars containing events as WebDAV collections.


This allows users to publish and subscribe to calendars, share them collaboratively, synchronize between multiple users and synchronize between multiple devices. The CalDAV standard is an implementation of iCal on a WebDAV server.
For details on how to configure Calendar for Apple MacOS with Zimbra Collaboration 8.7, 8.6, 8.5, or 8.0, see:


When using CalDAV, all of the user's calendars are added to iCal.
    https://wiki.zimbra.com/index.php?title=Accessing_Zimbra_Collaboration_Server_with_iCal_and_Calendar
 
''The following archive material is maintained for reference for use with obsolete versions of Zimbra.''
 
Zimbra 5.0 Supports the CalDAV standard. This allows users to publish and subscribe to calendars, share them collaboratively, synchronize between multiple users and synchronize between multiple devices.
 
The CalDAV standard is an extension to the WebDAV standard for accessing calendars on a WebDAV server.  Apple's iCal.app client (called Calendar in more recent versions of MacOS) supports the CalDAV standard.
 
CalDAV models calendar events as HTTP resources in iCalendar format, and models calendars containing events as WebDAV collections.
 
When using CalDAV with iCal.app, all of the user's calendars are added to iCal.app


=Requirements=
=Requirements=
Line 11: Line 20:
#MacOS 10.5 or Higher  
#MacOS 10.5 or Higher  


==Older MacOS==
==Zimbra Connector for iSync==
iCal on Tiger and older release only support ics import and export, not the full CalDAV.  The ics import mode is not compatible with CalDAV at all, and the usage is completely different.


In order to use ics import mode, first the user needs to export the calendar folder as ics, save to a file, then import the file into  the target calendar applicationUsing ics import mode, the changes made to the 3rd party calendar is saved as a local copy,  and ''does not automatically synchronize with Zimbra server''.
'''NoteThis connector is not supported with modern versions of Zimbra. CalDAV should be used instead.'''


When using CalDAV client, the changes are immediately saved to the server, unless the client is run in the offline mode.  There is no manual file based synchronization needed as with ics import mode.
The Zimbra Connector for iSync syncs Zimbra calendars to iCal for Tiger (10.4) and Leopard (10.5). The sync is done using SOAP instead of CalDAV -- unless you are running Mac OS 10.5 or previous and you you care about sync'ing contacts in addition to calendars, choose iSync. Otherwise, don't bother with with it, and setup your calendars as CalDAV calendars in iCal.
 
==Zimbra Connector for iSync==
The Zimbra Connector for iSync syncs Zimbra calendars to iCal for Tiger (10.4) and Leopard (10.5). However, the sync is done using SOAP and not CalDAV.


=Configuration=
=Configuration=
iCal supports CalDAV principal concept, and the URL to use is simply


http(s)://
In Leopard (10.5), open iCal and go to: Preferences > Accounts. Then:
'''
Note: You must not append anything after the servername when using iCal. There is an iCal bug that will cause it to fail. The URL should look like: http://host.server.com and not http://host.server.com/'''


Using the supplied username and password it can discover the user's calendar.
* Click the + (plus sign) to add an acocunt
* Enter a description; and enter the Zimbra username and password
* Click the arrow to expand "Server Settings"
* For the Account URL enter: <tt>http(s)://<server></tt>, in other words,<tt><nowiki>https://mail.example.com</nowiki></tt> -- iCal supports CalDAV principal concept so you'll notice that iCal will expand it to say:  <tt><nowiki>http(s)://<server>/principals/users/<username></nowiki></tt>


For other clients, users may need to add &amp;amp;quot;Calendar&amp;amp;quot; at the end of the URL to point to the calendar folder. e.g.
''Note: You must not append anything after the servername when using iCal. There is an iCal bug that will cause it to fail. The URL should look like: http://host.server.com and not http://host.server.com/''


http(s):// /dav/ /Calendar
* You're done -- hit Add.


#On Leopard (10.5), open iCal.
=Errors due to self-signed certificates=
#From the Menubar, choose &amp;amp;quot;iCal&amp;amp;quot;(Next to the Apple menu)
If your Zimbra server is using a self-signed certificate the subsciption to the server may fail with error -9813. In this case browse to your Zimbra server via Safari (using https) - accept the offered certificate permanently in all instances and close and reopen iCal.
#Choose &amp;amp;quot;Preferences&amp;amp;quot;
#Choose &amp;amp;quot;Accounts&amp;amp;quot;
#Click the + (plus sign) to add an account
#Give the account a Description
#Enter your Zimbra username
#Enter your Zimbra password
#Click the arrow to expand server settings
#Enter the Account URL in the syntax above select &amp;amp;quot;add&amp;amp;quot; and the Zimbra server will return the complete URL required - do not edit the URL and select &amp;amp;quot;add&amp;amp;quot; again if required
#Click Add


=Issues and Resources=
Reference: http://discussions.apple.com/thread.jspa?threadID=1505865&tstart=149


There is a known issue with iCal accepting Self Signed Certificates. If you are running the Zimbra server in https mode only, and have a self signed certificate, you may encounter: &amp;amp;amp;#39;&amp;amp;amp;#39;&amp;amp;amp;#39;Unexpected secure name resolution error (code -9813)&amp;amp;amp;#39;&amp;amp;amp;#39;&amp;amp;amp;#39;. You can resolve this issue by allowing http access, or purchasing a certificate by a source that is trusted.
==Older MacOS (Tiger and older) ==
iCal on Tiger and older release only support ics import and export, not the full CalDAV. The ics import mode is not compatible with CalDAV at all, and the usage is completely different.


http://www.zimbra.com/forums/administrators/16397-caldav-issue-leopard.html
In order to use ics import mode, first the user needs to export the calendar folder as ics, save to a file, then import the file into  the target calendar application. Using ics import mode, the changes made to the 3rd party calendar is saved as a local copy,  and ''does not automatically synchronize with Zimbra server''.


When using CalDAV client, the changes are immediately saved to the server, unless the client is run in the offline mode.  There is no manual file based synchronization needed as with ics import mode.
=Resources=
http://www.zimbra.com/forums
http://www.zimbra.com/forums
 
http://caldav.calconnect.org/
http://ietf.osafoundation.org/caldav/
http://ietf.osafoundation.org/caldav/
http://wiki.zimbra.com/index.php?title=CalDav_and_Mulberry - CalDAV Clients for Other Operating Systems


[[Category:OSX]]
[[Category:OSX]]
[[Category:Clients]]
[[Category:Clients]]

Latest revision as of 14:54, 19 September 2016

Introduction

For details on how to configure Calendar for Apple MacOS with Zimbra Collaboration 8.7, 8.6, 8.5, or 8.0, see:

   https://wiki.zimbra.com/index.php?title=Accessing_Zimbra_Collaboration_Server_with_iCal_and_Calendar

The following archive material is maintained for reference for use with obsolete versions of Zimbra.

Zimbra 5.0 Supports the CalDAV standard. This allows users to publish and subscribe to calendars, share them collaboratively, synchronize between multiple users and synchronize between multiple devices.

The CalDAV standard is an extension to the WebDAV standard for accessing calendars on a WebDAV server. Apple's iCal.app client (called Calendar in more recent versions of MacOS) supports the CalDAV standard.

CalDAV models calendar events as HTTP resources in iCalendar format, and models calendars containing events as WebDAV collections.

When using CalDAV with iCal.app, all of the user's calendars are added to iCal.app

Requirements

  1. Zimbra Collaboration Suite 5.0 RC2 or Higher
  2. MacOS 10.5 or Higher

Zimbra Connector for iSync

Note. This connector is not supported with modern versions of Zimbra. CalDAV should be used instead.

The Zimbra Connector for iSync syncs Zimbra calendars to iCal for Tiger (10.4) and Leopard (10.5). The sync is done using SOAP instead of CalDAV -- unless you are running Mac OS 10.5 or previous and you you care about sync'ing contacts in addition to calendars, choose iSync. Otherwise, don't bother with with it, and setup your calendars as CalDAV calendars in iCal.

Configuration

In Leopard (10.5), open iCal and go to: Preferences > Accounts. Then:

  • Click the + (plus sign) to add an acocunt
  • Enter a description; and enter the Zimbra username and password
  • Click the arrow to expand "Server Settings"
  • For the Account URL enter: http(s)://<server>, in other words,https://mail.example.com -- iCal supports CalDAV principal concept so you'll notice that iCal will expand it to say: http(s)://<server>/principals/users/<username>

Note: You must not append anything after the servername when using iCal. There is an iCal bug that will cause it to fail. The URL should look like: http://host.server.com and not http://host.server.com/

  • You're done -- hit Add.

Errors due to self-signed certificates

If your Zimbra server is using a self-signed certificate the subsciption to the server may fail with error -9813. In this case browse to your Zimbra server via Safari (using https) - accept the offered certificate permanently in all instances and close and reopen iCal.

Reference: http://discussions.apple.com/thread.jspa?threadID=1505865&tstart=149

Older MacOS (Tiger and older)

iCal on Tiger and older release only support ics import and export, not the full CalDAV. The ics import mode is not compatible with CalDAV at all, and the usage is completely different.

In order to use ics import mode, first the user needs to export the calendar folder as ics, save to a file, then import the file into the target calendar application. Using ics import mode, the changes made to the 3rd party calendar is saved as a local copy, and does not automatically synchronize with Zimbra server.

When using CalDAV client, the changes are immediately saved to the server, unless the client is run in the offline mode. There is no manual file based synchronization needed as with ics import mode.

Resources

http://www.zimbra.com/forums http://caldav.calconnect.org/ http://ietf.osafoundation.org/caldav/

Jump to: navigation, search