Managed DAVx⁵

With Managed DAVx⁵, you can configure DAVx⁵ centrally for a whole organization.

Managed configuration

Managed DAVx⁵ allows you to manage DAVx⁵ clients centrally by using these configuration methods (in order of precedence):

  1. EMM restrictions (recommended)
  2. network configuration: fixed URL (QR code)
  3. network configuration: unicast DNS
  4. network configuration: Zeroconf (DNS-SD)
  5. local configuration file

This configuration is used in the Managed DAVx⁵ UI and for new Managed DAVx⁵ accounts.

Existing Managed DAVx⁵ accounts on your devices won't be modified when the managed configuration is changed.

Configuration by EMM restrictions (Android Enterprise)

Android Enterprise is the recommended method to configure Managed DAVx⁵. With Android Enterprise, IT departments can deploy apps to managed devices and configure them in a standardized way using EMM software. Apps are configured by restrictions which can be set in the EMM software for every deployed app.

Network configuration

There are three methods of network configuration:

  • fixed URL
  • unicast DNS
  • Zeroconf (DNS-SD)

Network configuration requires managed Android devices to be connected to the network where the configuration file can be found. Usually, this is a WiFi and/or VPN connection. The following paragraphs apply to all network configuration methods:


When accessing the configuration file, PKI is used to verify the TLS certificate, so a self-signed certificate won't work without adding it to the Android device first. We recommend to put the configuration file to a location which is accessible over a trusted certificate. You can then define custom trusted certificates in the configuration file.


Two types of caching are used to cache Managed DAVx⁵ configuration when it's taken from the network:

  1. configuration cache and
  2. HTTP cache.

Configuration cache: Managed DAVx⁵ caches the configuration file which is fetched from the network so that Managed DAVx⁵ configuration is available when there is no network access (and for the time when Managed DAVx⁵ has been started, but the new network configuration is not ready yet). The cache will be overwritten when a new configuration file is downloaded. To reset the cache without a new configuration file, use: Managed DAVx⁵ / About/License / Managed configuration / Reload configuration.

HTTP cache: The configuration file is cached when it has been downloaded from the network according to the rules of the HTTP protocol. For instance, if the Web server which hosts the configuration file returns a freshness period of one hour, Managed DAVx⁵ will always use the cached version for one hour. However, the configuration file will be downloaded at least once a day (max-age: 1 day) to avoid problems caused by obsolete configuration files. If there is no Expires, the cache will use If-Match and If-Unmodified-Since.

It's advisable to set an expiration time for the configuration file on the Web server (for instance, one hour) explicitly to avoid unnecessary network traffic every time Managed DAVx⁵ is started on a device.

Configuration by fixed URL/QR code

The simplest method to configure Managed DAVx⁵ over the network is to use a fixed configuration file URL, which can for example be provided as a QR code. This method can be used if you don't want to use automatic discovery of the Managed DAVx⁵ configuration file.

To set a network configuration URL, an ACTION_VIEW Intent with the configuration file URL (ending in davdroid-config.json) has to be called on the Android device. To do so, you can

  • scan the QR code of the configuration file URL, then open it with Managed DAVx⁵ (not your browser)
  • link to the configuration file on some page in your Intranet, and use your browser to open it with Managed DAVx⁵

You can see and reset the current configuration file URL in Managed DAVx⁵ / About/License / Managed configuration.

Summary: To get Managed DAVx⁵ running with a fixed configuration URL, you need to

  1. upload the Managed DAVx⁵ configuration file to a HTTPS server in the network (file name: davdroid-config.json),
  2. generate a QR code for this URL,
  3. scan the QR code on the Android device (you may have to install a QR code scanner app first),
  4. start Managed DAVx⁵ and make sure everything works as expected.

Configuration by unicast DNS

Managed DAVx⁵ tries to resolve the SRV and TXT path records of davdroid-configs.local in the local network. In case of success, the resulting URL (https scheme, domain and host taken from SRV, path taken from TXT path, or / else) is used to fetch Managed DAVx⁵ configuration.

An example DNS configuration could look like this:


davdroid-configs.local   IN SRV 1 0 443
davdroid-configs.local   IN TXT "path=/davdroid/davdroid-config.json"


In this case, Managed DAVx⁵ would try to access the configuration file at

Summary: to get Managed DAVx⁵ running with unicast DNS, you need to

  1. upload the Managed DAVx⁵ configuration file to a HTTPS server in the network,
  2. add SRV and TXT DNS records for davdroid-configs.local in your network DNS server/forwarder,
  3. start Managed DAVx⁵ and make sure everything works as expected.

Configuration by Zeroconf (DNS-SD)

Managed DAVx⁵ can discover a service called davdroid-configs._tcp using DNS-SD. The network configuration file URL (https scheme) will be built from the host and path parts of TXT records (the SRV record is not used because the discovery service is not the same as the referenced configuration). If no host is specified, the host name of the host running the avahi service is used. If no path is specified, / will be used.

You can use any DNS-SD server. If you use avahi, the configuration file could be put into /etc/avahi/services and look like this:


<?xml version="1.0" standalone='no'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
  <name>Managed DAVx⁵ configuration</name>
  <service protocol="ipv4">


In this case, Managed DAVx⁵ would try to download the configuration file from

Summary: To get Managed DAVx⁵ running with DNS-SD, you need to

  1. upload the Managed DAVx⁵ configuration file to some Web server in the network,
  2. install and start a DNS-SD server like avahi on a server in the network (for instance, the Ubuntu avahi-daemon package),
  3. add the _davdroid-configs._tcp service with host and path TXT records,
  4. if necessary, allow DNS-SD in the firewall rules,
  5. start Managed DAVx⁵ and give it some time to detect and download the configuration.

Local configuration file

Managed DAVx⁵ watches the device for a file named davdroid-config.json in the app-private directory (package identifier: com.davdroid.managed) on the external storage, for instance /storage/emulated/0/Android/data/com.davdroid.managed/files/davdroid-config.json.

If no other configuration method is active, you can put a configuration file to this location (using a regular file manager app or adb). Changes in this file will be applied immediately. This method is only recommended for debugging/testing purposes, for instance if you want to test the configuration file without the influence of potential networking problems.

Configuration variables

Managed DAVx⁵ configuration variables
licensetext*license data (JSON)
license_signaturetext*license signature (Base64)
organizationtextorganization display name; shown in app drawer and login activity
logo_urltext (URL)organization logo; shown in login activity; must be publicly accessible without authentication
support_homepage_urltext (URL)URL of intranet page with details on how to use Managed DAVx⁵ in this organization and how to get internal support; shown in app drawer
support_email_addresstext (email address)internal support email address – shown in app drawer and some notifications
support_phone_numbertext (phone number)internal support phone number – shown in app drawer and some notifications
login_introductiontext (simple HTML)message that will be shown when the user adds an account; may contain simple HTML like paragrahps, bold text and links
login_base_urltext (URL)*

base URL for CalDAV/CardDAV service discovery when an account is added


login_user_nametextdefault user name when an account is added – only useful with EMM configuration when EMM can pre-fill restrictions from user details
login_certificate_aliastextif provided, client certificates will be used for authentication (instead of user name/password); value of this field will be pre-selected (if available)
max_accountsinteger*maximum number of accounts – no new accounts can be created when this number of accounts is reached
override_proxyboolean*false = system proxy settings are used
true = system proxy settings are ignored and override_proxy_host and override_proxy_port are used instead
override_proxy_hosttext (host name)HTTP proxy host name
override_proxy_portint (port number)HTTP proxy port number

false = DAVx⁵ will only sync when a WiFi connection is active
true = DAVx⁵ will sync regardless of the connection type

wifi_only_ssidstext (comma-separated list)

when set, DAVx⁵ will only sync when device is connected to one of these WiFis

only used when wifi_only is true; example: wifi1,wifi2,wifi3

contact_group_methodstring: CATEGORIES or GROUP_VCARDS

CATEGORIES = contact groups are stored as per-contact category tags
GROUP_VCARDS = contact groups are separate VCards

set as required by your server and/or other clients

manage_calendar_colorsbooleanfalse = DAVx⁵ will copy detected calendar colors to the device at every sync
true = DAVx⁵ won't change local calendar colors at every sync

false = DAVx⁵ won't synchronize event colors
true = DAVx⁵ will synchronize event colors

setting to true causes some default calendar apps; make sure that your preferred calendar app is working with this setting

*… required

Configuration file syntax

A Managed DAVx⁵ configuration file contains configuration variables in JSON format, like this:


  "license": "<escaped JSON, don't change this>",
  "license_signature": "<don't change this>",
  "organization": "bitfire",
  "logo_url": "",
  "support_homepage_url": "",
  "support_email_address": "",
  "support_phone_number": "+1 234 56789",
  "login_base_url": "",
  "max_accounts": 1,
  "override_proxy": false,
  "wifi_only": true,
  "wifi_only_ssids": "wifi1,wifi2",
  "contact_group_method": "GROUP_VCARDS",
  "manage_calendar_colors": true,
  "event_colors": false

Last updated: 30 Dec 2018