Difference between revisions of "Auto-provisioning"
(Created page with "CalDAV-Sync and CardDAV-Sync support auto-configuration and painless account setup. This is particular useful if you run a CalDAV/CardDAV server for an organization with ...") |
|||
| Line 1: | Line 1: | ||
[[CalDAV-Sync]] and [[CardDAV-Sync]] support auto-configuration and painless account setup. This is particular useful if you run a CalDAV/CardDAV server for an organization with many users. Auto-configuration allows users to set up the account without knowledge of any server details (and without all the typing). | [[CalDAV-Sync]] and [[CardDAV-Sync]] support auto-configuration and painless account setup. This is particular useful if you run a CalDAV/CardDAV server for an organization with many users. Auto-configuration allows users to set up the account without knowledge of any server details (and without all the typing). | ||
| + | Auto-configuration is still under development. Future releases will allow to set more options automatically up to a degree where almost no additional user-interaction is necessary. | ||
== How it works == | == How it works == | ||
Revision as of 11:16, 23 March 2012
CalDAV-Sync and CardDAV-Sync support auto-configuration and painless account setup. This is particular useful if you run a CalDAV/CardDAV server for an organization with many users. Auto-configuration allows users to set up the account without knowledge of any server details (and without all the typing). Auto-configuration is still under development. Future releases will allow to set more options automatically up to a degree where almost no additional user-interaction is necessary.
How it works
To use auto-configuration place a link matching this scheme on your website:
caldav[s]://[username[:password]@][servename][:port][/path][#options] or carddav[s]://[username[:password]@][servename][:port][/path][#options]
When you open this link from your phone's browser the CalDAV-Sync or CardDAV-Sync account setup will be invoked with these settings.
See below for some examples.
The details
Most parts of the link scheme are optional (depending on your server setup). Only the URI scheme and the server name are always mandatory.
- caldavs:// or caldav://
- prefix for CalDAV accounts using SSL or without SSL
- carddavs:// or carddav://
- prefix for CardDAV accounts using SSL or without SSL
- [username] or [username:password]
- (optional) the username and password to use for authentication (note: ":","@" and "/" in username or password have to be url-encoded). Beware: including the password may have serious security implications and is not recommended!
- [servername]
- the name of your server
- [:port]
- (optional) The port to connect to, mandatory if you use a non-standard port.
- [/path]
- (optional) The path to the CalDAV or CardDAV root, the principal home or the calendar/address book home. You can omit this if you use a .well-know redirection or if you don't run your server in a sub-path.
- [#options]
- (optional) A set of default account options. Multiple options have to be concatenated by an ampersand (&). Currently the following options are supported (more options will follow):
- preemptive_auth
- (currently CalDAV-Sync only) Enable preemptive authentication by default.
- enforce_dtend
- (CalDAV-Sync only) Always store a DTEND field in the event file, never use DURATION. This is a workaround for Oracle Convergence servers.
Examples
The following examples will set up accounts for the SOGo demo server
- full path to DAV root
- caldav://sogo-demo.inverse.ca/SOGo/dav
- carddav://sogo-demo.inverse.ca/SOGo/dav
- with username and port
- caldav://sogo1@sogo-demo.inverse.ca:80
- carddav://sogo1@sogo-demo.inverse.ca:80
- with username and password
- caldav://sogo1:sogo1@sogo-demo.inverse.ca
- carddav://sogo1:sogo1@sogo-demo.inverse.ca
- Note: Although it's supported, it's not recommended to use this because it contains your password in plain text and everyone with access to the page can read it!
Use the following to sync using SSL (with an alternative SSL-port), preemptive authentication and enforced DTEND. The login in this example is username@example.com (note the encoded "@")
